Simon
>
>
> -Original Message-
> From: Justin Schoeman [mailto:[EMAIL PROTECTED]
> Sent: Sat 2/18/2006 11:12 AM
> To: axis-user@ws.apache.org
> Cc: Simon Fell
> Subject: Re: Consuming Axis2 webservice with c# client?
>
> If that is the case, how do I
Title: RE: Consuming Axis2 webservice with c# client?
xml schema type attribute is serialized with wrong namespace (should be http://www.w3.org/2001/XMLSchema-instance, is currently not namespace qualified).
to test it, you could write a quick jsp that returns the modifed response and point
EMAIL PROTECTED]
Sent: Sat 2/18/2006 11:12 AM
To: axis-user@ws.apache.org
Cc: Simon Fell
Subject: Re: Consuming Axis2 webservice with c# client?
If that is the case, how do I convince the Axis server to append the
'xsi:' to the type? Is there a simple way, or do I need to hack the
gene
Fell
Subject: Re: Consuming Axis2 webservice with c# client?
If that is the case, how do I convince the Axis server to append the
'xsi:' to the type? Is there a simple way, or do I need to hack the
generated Axis code?
Thanks,
Justin
Simon Fell wrote:
> type="GenericDevic
Simon
-Original Message-
From: Justin Schoeman [mailto:[EMAIL PROTECTED]
Sent: Fri 2/17/2006 8:08 AM
To: axis-user@ws.apache.org
Subject: Re: Consuming Axis2 webservice with c# client?
The WSDL and XSD files are attached. I had to edit the WSDL from the
published version by filling
Title: RE: Consuming Axis2 webservice with c# client?
type="GenericDeviceID" should be xsi:type="GenericDeviceID"
Cheers
Simon
-Original Message-
From: Justin Schoeman [mailto:[EMAIL PROTECTED]]
Sent: Fri 2/17/2006 8:08 AM
To: axis-user@ws.apache.org
Subject:
No, this isn't the same problem. I suggest you ask your question on a .NET discussion list. .NET should be able to interpret the response.AnneOn 2/18/06,
Justin Schoeman <[EMAIL PROTECTED]> wrote:
How could it possibly expect an abstract type - an abstract type has noimplementation?Is this not pos
How could it possibly expect an abstract type - an abstract type has no
implementation?
Is this not possibly the interop problem that was mentioned before (I am
sure I read about it on the list, but can not find it again), where .net
clients had problems understanding a type attribute when the
Hmmm...Well, this type definiton: A response containing customer details.
type="i0:ConfirmCustResult"/> doesn't indicate that the element should us
WSDL?On 2/17/06, Justin Schoeman <[EMAIL PROTECTED]> wrote:
Further information, we just managed to get the debug messages out, andgot the extended error:Unhandled Exception: System.InvalidOperationException: There is an errorin XML document (1, 877). ---> System.InvalidOperationException
: Thespec
Further information, we just managed to get the debug messages out, and
got the extended error:
Unhandled Exception: System.InvalidOperationException: There is an error
in XML document (1, 877). ---> System.InvalidOperationException: The
specified type is abstract: name='DeviceID',
namespace=
Hi all,
I seem to remember a discussion on this a while ago, but cannot seem to
find it now.
I am trying to use an Axis2 web service (generated from WSDL) from a
Visual C# client (also generated from the WSDL. Everything works fine
until the client starts parsing the response XML, when it g
12 matches
Mail list logo
