r the confusion
Ann, thanks for all your help
Karl
-Original Message-
From: Schwarz, Karl [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 19, 2005 7:53 AM
To: axis-user@ws.apache.org
Subject: RE: Exception parsing complex data type
Well I've tried a few different tracks and I am
Well I've tried a few different tracks and I am still left with the same
original problem, that is an org.xml.sax.SAXException: Invalid element exception
The wsdl I am using is a follows:
http://examples.com/PhotoCatalog";
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
xmlns:soap="http://sch
mended approach, given the current state of AXIS?
regards,
Karl
-Original Message-
From: Schwarz, Karl [mailto:[EMAIL PROTECTED]
Sent: Monday, April 18, 2005 7:31 AM
To: axis-user@ws.apache.org; Anne Thomas Manes
Subject: RE: Exception parsing complex data type
Anne,
Thanks for the hel
s.utils.JavaUtils.convert(_resp, java.lang.String.class);
}
}
} catch (org.apache.axis.AxisFault axisFaultException) {
throw axisFaultException;
regards
Karl
-Original Message-
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Sent: Friday, April 15, 2005 2:24 PM
To: axis-user@ws.apache.or
It turns out your WSDL isn't valid.
Tell me if this is correct::
For the addPhoto operation, you want to pass in
- the customer name (string)
- a photo ID (int)
- a photo (as an attachment)
And you want to get in return
- status (string) (currently you're trying to return this as an
attachmen
Karl,
I probably wouldn't select a SOAP w/ Attachments WSDL as my first test
case, but perhaps you enjoy self abuse... (I'm not sure that Axis
supports the WS-I Attachments profile.)
In any case, the first error is caused by the fact that Axis generated
an RPC style message (it generated the "add