Andrea
if you could display your full wsdl we could see what your xsd maps to..
Molte Grazie
Martin
__
Disclaimer and confidentiality note
Everything in this e-mail and any attachments relates to the official business
of Sender. This transmission is
There is no element named "boolean" in the XML Schema namespace, only
a type named boolean. You have to provide an element QName for the
message part in a doc/lit web service, so you must define an element
that is of type boolean if that's the type you want. It must be in
some namespace you contr
When using document style, your message parts must reference elements
rather than types.
Anne
On 4/10/07, Rudolph, Troy <[EMAIL PROTECTED]> wrote:
Hi Everyone,
I created a WSDL file to describe an experimental web service that I am
building. However, when I generated the code from the WSDL
When using doc style, all content that goes in the SOAP Body must be defined as an element, but the attachments are defined as types. So you must define elements to contain your fileName and return strings. e.g., the messages should be defined like so...
An
this is exactly swa specification... MIME message or not?On 2/18/06, Xinjun Chen <[EMAIL PROTECTED]> wrote:
I am not sure what your problem is. I found the following snippet from your WSDL file.
You use doc-lit style, yet your message have two parts. I am not sure wheth
I am not sure what your problem is. I found the following snippet from your WSDL file.
You use doc-lit style, yet your message have two parts. I am not sure whether this will cause problem. But anyway, this is not a good practice to have more than one part in a message.
rodriguo, i think that the service is deployed correctly... this is the wsdd. any suggests???simone
xmlns="
http://xml.apache.org/axis/wsdd/" xmlns:java="http://xml.apache.org/axis/wsdd/providers/java">
http://www.informatica.uniroma2.it/WebDisk/wsdl"/> http://www.
thank you for the information i will tryregardssimoneOn 2/16/06, Rodrigo Ruiz <[EMAIL PROTECTED]
> wrote: From the logs you give in your post, it seems you are trying to catch
the wrong error :-)The NoSuchMethodException is not an error condition. If you watch theaxis source code you will see t
From the logs you give in your post, it seems you are trying to catch
the wrong error :-)
The NoSuchMethodException is not an error condition. If you watch the
axis source code you will see that it is just a first attempt to get a
factory instance. Just after this log entry, there is a second
Hi Simone,
Take a look at another axis example: samples/swa
It took me several days to notice this example was there :-D
Regards,
Rodrigo Ruiz
thanks for the link anne, there are some code samples but there isn't a wsdl example... where can i find it?SimoneOn 2/16/06, Anne Thomas Manes
<[EMAIL PROTECTED]> wrote:Check the Wiki for information on using attachments.
http://wiki.apache.org/ws/FrontPage/Axis.(scroll down to the section on Att
Check the Wiki for information on using attachments.http://wiki.apache.org/ws/FrontPage/Axis.(scroll down to the section on Attachments)Anne
On 2/16/06, Simone Bonazzoli <[EMAIL PROTECTED]> wrote:
sorry the element uploadRequest is wrong :)forget it :)On 2/16/06, Simone Bonazzoli <
[EMAIL PROTE
sorry the element uploadRequest is wrong :)forget it :)On 2/16/06, Simone Bonazzoli <[EMAIL PROTECTED]
> wrote:however, this is my xsd:http://www.informatica.uniroma2.it/WebDisk
" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:tns="
http://www.informatica.uniroma2.it/WebDisk
"
however, this is my xsd:http://www.informatica.uniroma2.it/WebDisk
" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://www.informatica.uniroma2.it/WebDisk
" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/
how i can define my binding to use attachments??? i try the SWA approach but i have a problem with axis... a few weeks ago i sent few mail but i didn't resolve my error... so i try the attachments sample (in the samples direcotry of axis distribution) but there isn't wsdl of the example so i try to
My guess is that it's your WSDL, but we need the imported XSD to make a final determination.One error that I see in the WSDL:
When using document style, a message part must reference an element, not a type. This error could be causing the NPE.
Also suspect is the reference to the el
Anybody run into this?
markg
-Original Message-
From: Griffin, Mark
Sent: Monday, February 13, 2006 10:39 AM
To: axis-user@ws.apache.org
Subject: WSDL2Java Bug?
I've run into an issue with Axis 1.3 using WSDL2Java. It appears to
work okay when I use a wsdl file that imports an xml sch
Hello!
Sorry I forgot attach the wsld, here is:
http://schemas.xmlsoap.org/wsdl/";
xmlns:conv="http://www.openuri.org/2002/04/soap/conversation/";
xmlns:cw="http://www.openuri.org/2002/04/wsdl/conversation/";
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/";
xmlns:jms="http://www.openuri.o
it produced code from which I could
easily remove MyUnwantedElement-related content.
Jeff Lawson
- Original Message -
From: "Anne Thomas Manes" <[EMAIL PROTECTED]>
To:
Sent: Saturday, May 28, 2005 9:03 AM
Subject: Re: WSDL2Java bug in Axis 1.2 (and 1.2.1)
J
Jeff,
None of these structures is valid schema. Could you try your test
again with valid structures?
This is valid:
And this is valid:
Thanks,
Anne
On 12/28/04, Jeff <[EMAIL PROTECTED]> wrote:
>
> Here's a WSDL2Java bug in Axis 1.2 (and 1.2.1)
20 matches
Mail list logo
