Domino consumes web service URL encode

I have a Domino agent that uses Axis jar files to consume asp.net web service. This is working. I have string parameters that are passed to the web service.

The problem is if there is an “apostrophe” in a string parameter, java agent throws an error. I am guessing I need to encode the string. When I encode string there’s no error but the destination string saved is not right, IE.,

string is “This is John’s file.”

destination is “This%20is%20John%27s%20file.”

What is going on? Why doesn’t the destination string look the same way?

Subject: Domino consumes web service URL encode

From the @WebDbName Topic of the Lotus Designer Help Database:“URL encoding changes most special characters to the text %xx where xx is a hexadecimal number representing the value of the character. In particular, spaces are changed to %20.”

And apostrophes are changed to %27.

Subject: RE: Domino consumes web service URL encode

I’m familiar with URLEncoding but my question is really about the parameters passed to the web service. If I am passing a string that is encoded, then is there something on the web service end that needs to maybe decode the string?

Subject: RE: Domino consumes web service URL encode

A few questions…

  1. What error is thrown by the Java Agent when you don’t encode the URL?

  2. What exactly are you attempting to do with this string?

…depending on the latter, it does seem as though you would need to decode - depending upon what you’re actually trying to do with that string.

Subject: Domino consumes web service URL encode

Hi ,Are you consuming the web services which is SSL .

I want to know how to code a web service which ssl secured .

THanks

Sushant

Subject: Re: Web Services (WSDL) & SSL

Assuming Domino is the Web Server in this picture, its HTTP Task needs to be configured for SSL; which involves the configuration of Certificate Authority(ies). Once both the Server (and then any clients) have the certs properly configured, you should only need to edit the WSDL of your Web Service to use “https” instead of “http”.