Hi,
I managed to figure out this. I used the Java class annotated with @WebService and I was specifying the wsdl written by me. I've let it generate it's own wsdl and it's working just fine now.
Diana Chinces
________________________________
From: Karl Jóhann Pálsson <karlp_at_vodafone.is>
To: "dev_at_jax-ws.dev.java.net" <dev_at_jax-ws.dev.java.net>
Sent: Tue, February 2, 2010 4:01:16 PM
Subject: RE: JAX-WS Null Parameter problem
I would suggest that your soap request is not, in fact,
correct. If you have the slightest thing wrong with namespaces, you'll get a
null/0 input parameter, instead of what you were expecting.
From:Chinces Diana
[mailto:chincesdiana_at_yahoo.com]
Sent: Tuesday, February 02, 2010 1:14 PM
To: dev_at_jax-ws.dev.java.net
Subject: Re: JAX-WS Null Parameter problem
Yes,
I know that.
My questions was how do I get to send to parameters? Even though the SOAP
request is correct I still receive the null/0 parameters.
Do you have any suggestions?
Diana
Chinces
________________________________
From:Potociar Marek
<Marek.Potociar_at_Sun.COM>
To: dev_at_jax-ws.dev.java.net
Sent: Tue, February 2, 2010 3:11:43 PM
Subject: Re: JAX-WS Null Parameter problem
I would guess it is because null is not a valid primitive value.
Regards,
Marek
On 2.2.2010, at 13:46, Chinces Diana wrote:
Hi,
I have encountered the following issue when developing a Java Web Service with
JAX-WS: when calling the web method I always receive null parameters as input.
If I use primitive types for the parameter types I get 0 instead of null.
Do you have any idea why? Any suggestions would be appreciated.
Thanks,
Diana Chinces