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 xmlns
attributes were also passed. I seem to remember there being a simple
config file change to enable compatibility...
?
Thanks,
Justin
Anne Thomas Manes wrote:
Hmmm...
Well, this type definiton:
<complexType name="ConfirmCustomerResp">
<annotation>
<documentation> A response containing customer details.
</documentation>
</annotation>
<complexContent>
<extension base="b0:BaseResp">
<sequence>
<element minOccurs="1" maxOccurs="unbounded"
name="confirmCustResult"
type="i0:ConfirmCustResult"/>
</sequence>
</extension>
</complexContent>
</complexType>
doesn't indicate that the element should use GenericDeviceID in place of
the abstract DeviceID type. (b0:BaseResp specifies that ClientID is of
type DeviceID.) You are correct that it should work, though, because the
type is explicitly specified in the element. But perhaps the generated
.NET client is confused because it's expecting the abstract type.
On 2/17/06, *Justin Schoeman* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
The WSDL and XSD files are attached. I had to edit the WSDL from the
published version by filling in the soapAction name for the operations
that we use. I am not sure of the significance of this field, and why
it was left out in the original service, but without it, the generated
clients get EPR not found errors. Modifying this wouldn't cause this
problem though, would it?
The WSDL files come from a standards body, and I am not sure if they
were generated from any specific application.
Thanks!
Justin
Anne Thomas Manes wrote:
> WSDL?
>
> On 2/17/06, *Justin Schoeman* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
> <mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>>
wrote:
>
> 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='http://www.nrs.eskom.co.za/xmlvend/base/2.0/schema', at
> <clientID xmlns='
http://www.nrs.eskom.co.za/xmlvend/base/2.0/schema'>.
>
> However, if you look at the generated xml, the full field is:
> clientID xmlns="
http://www.nrs.eskom.co.za/xmlvend/base/2.0/schema
> <http://www.nrs.eskom.co.za/xmlvend/base/2.0/schema>"
> type="GenericDeviceID" id="12345" />
>
> so the very next attribute sets the explicit type. Surely
this is an
> acceptable response?
>
> Thanks,
>
> Justin
>
>
> Justin Schoeman wrote:
> > 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
gives
> an error
> > 'There is an error in XML document(1,877)'. Position 877
in the
> response
> > xml is the first character name of the first element
withing the
> complex
> > return type. The start of the xml is included below. If
> anybody has
> > any ideas, please let me know!
> >
> > Thanks!
> >
> > Justin
> >
> > XML Response:
> > <?xml version=' 1.0' encoding='utf-8'?>
> > <soapenv:Envelope
> > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
> > xmlns:wsa=" http://schemas.xmlsoap.org/ws/2004/08/addressing";>
> > <soapenv:Header>
> > <wsa:Action
> > mlns:wsa=" http://schemas.xmlsoap.org/ws/2004/08/addressing
> <http://schemas.xmlsoap.org/ws/2004/08/addressing
<http://schemas.xmlsoap.org/ws/2004/08/addressing>>">ConfirmCustomerRequest</wsa:Action>
> >
> > <wsa:ReplyTo
> >
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing
<http://schemas.xmlsoap.org/ws/2004/08/addressing>
>
"><wsa:Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:Address></wsa:ReplyTo>
> >
> > <wsa:From
> >
>
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing";><wsa:Address>
>
http://cohen:8080/axis2/services/XMLVendService2.0</wsa:Address></wsa:From>
> >
> > <wsa:MessageID
> > xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing
> <http://schemas.xmlsoap.org/ws/2004/08/addressing
<http://schemas.xmlsoap.org/ws/2004/08/addressing>>">A7E4A85F20AA66B0C4114018114390618</wsa:MessageID>
> >
> > </soapenv:Header>
> > <soapenv:Body>
> > <confirmCustomerResp
> > xmlns="
http://www.nrs.eskom.co.za/xmlvend/revenue/2.0/schema";>
> > <clientID xmlns="
http://www.nrs.eskom.co.za/xmlvend/base/2.0/schema";
> > type="GenericDeviceID" id="12345" />
> > <serverID xmlns="
http://www.nrs.eskom.co.za/xmlvend/base/2.0/schema";
> > ean="1" />
> > <terminalID
> xmlns=" http://www.nrs.eskom.co.za/xmlvend/base/2.0/schema";
> > type="GenericDeviceID" id="54321" />
> > <reqMsgID xmlns="
http://www.nrs.eskom.co.za/xmlvend/base/2.0/schema";
> > dateTime="2006-02-17 12:00:00" uniqueNumber="MSGID-0001" />
> > <respDateTime
> >
> xmlns="
http://www.nrs.eskom.co.za/xmlvend/base/2.0/schema";>2006-02-17T14:59:03.910+02:00</respDateTime>
>
> >
> > <confirmCustResult>
> > <custVendDetail address="here" contactNo="0123456789"
name="Mr JF
> > Schoeman" accNo="12345-67890" /></confirmCustResult>
> > </confirmCustomerResp>
> > </soapenv:Body></soapenv:Envelope>
>
>
