Hi Amila,
On May 8, 2010, at 8:54 PM, Amila Suriarachchi wrote:
>> The goal of not including a service element is spelled out in another
>> section of the wsdl docs:
>> http://www.w3.org/TR/wsdl20-primer/#adv-service-references . Our service is
>> very similar to the example service in that we
Hi Amila,
On May 8, 2010, at 8:25 PM, Amila Suriarachchi wrote:
>> On Fri, May 7, 2010 at 6:12 AM, Lev Lvovsky wrote:
>> Hello,
>>
>> I'm running a wsdl file through the wsdl2java.sh application and am running
>> into some unexpected problems.
>>
>> Below is pseudo-code of the stubbed client
That is by design: all characters in the range 0-31 are forbidden by
XML, except LF, CR and tab. This has nothing to do with encoding.
Andreas
On Mon, May 10, 2010 at 14:45, Stadelmann Josef
wrote:
>
>
> That is the exception I get when valid UTF encoded text containing invalid
> XML characters
That is the exception I get when valid UTF encoded text containing
invalid XML characters are attempted to be returned to the client!
TcpMonitor output:
HTTP/1.1 100 Continue
HTTP/1.1 400 Bad Request
Server: Apache-Coyote/1.1
Content-Type: application/soap+xml;
action="http://w
Invalid XML Characters: when valid UTF8 does not mean valid XML
Googling for "valid xml characters" ANSWERED MY QUESTION TO SOME
DEGREE.
So let me related the problem I am faced with in a attempt that
somebody has a clever solution for us for all the folk reading t
Usually I work with JAX-WS Web Services and i developped JAX-WS handlers
for them.
Now, I have an Axis2 Web service and I would like to use the same handlers
: is it possible ?
When I try to configure it I get the following error ;
"cannot be cast to org.apache.axis2.engine.Handler"
because my h
Hi all,
my legacy server called by an axis2/J web service code passes an returns
to axis2 a long xml string.
This string is completed in the web service (Java code) and then
converted to an AXIOM OMElement type.
When the legacy server returns a , areal form feed character, Ascii
Code 12, then
