Re: Soap request issue when a parameter is null
I have done what you suggested and it seems to work perfectly. Thanks a lot! But does it mean that one should'nt use the auto generated wsdl file ? Luuzz wrote: Thanks a lot for the quick reply. I use the RPCMessageReceiver indeed. Do you think that i should use another one ? I am going to try to modify the wsdl file and keep you informed !! keith chapman wrote: I believe you are using the RPCMessageReceiver. There is a bug in the RPCMessageReceiver and I think this is what your hitting. As a workaround I suggest that u save the WSDL generated by axis2 and get rid of minoccurs=0 attribute that is present in all the types. drop the edited WSDL into the service archive and redeploy the service. Thanks, Keith. On Fri, Aug 1, 2008 at 4:10 PM, Luuzz [EMAIL PROTECTED] wrote: Hello, I am new using axis2. I have developped some services with it and it works really well. But i have some problems with my last one. The web method has many parameters. Some of them can be null. So when i call the method using a soap message not specifying the nillable parameters, the binding doesn't work well. For example the pi element of the soap message is bound to pj web method parameter. To make the service work, i have to use all the parameters in my soap request even if most of them have an empty value. It is very strange. I don't know if i am clear enough but i hope that you will help me. -- View this message in context: http://www.nabble.com/Soap-request-issue-when-a-parameter-is-null-tp18771917p18771917.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Keith Chapman Senior Software Engineer WSO2 Inc. Oxygenating the Web Service Platform. http://wso2.org/ blog: http://www.keith-chapman.org -- View this message in context: http://www.nabble.com/Soap-request-issue-when-a-parameter-is-null-tp18771917p18801425.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Soap request issue when a parameter is null
Hello, I am new using axis2. I have developped some services with it and it works really well. But i have some problems with my last one. The web method has many parameters. Some of them can be null. So when i call the method using a soap message not specifying the nillable parameters, the binding doesn't work well. For example the pi element of the soap message is bound to pj web method parameter. To make the service work, i have to use all the parameters in my soap request even if most of them have an empty value. It is very strange. I don't know if i am clear enough but i hope that you will help me. -- View this message in context: http://www.nabble.com/Soap-request-issue-when-a-parameter-is-null-tp18771917p18771917.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Soap request issue when a parameter is null
Thanks a lot for the quick reply. I am going to try this out as soon as possible and keep you informed !! keith chapman wrote: I believe you are using the RPCMessageReceiver. There is a bug in the RPCMessageReceiver and I think this is what your hitting. As a workaround I suggest that u save the WSDL generated by axis2 and get rid of minoccurs=0 attribute that is present in all the types. drop the edited WSDL into the service archive and redeploy the service. Thanks, Keith. On Fri, Aug 1, 2008 at 4:10 PM, Luuzz [EMAIL PROTECTED] wrote: Hello, I am new using axis2. I have developped some services with it and it works really well. But i have some problems with my last one. The web method has many parameters. Some of them can be null. So when i call the method using a soap message not specifying the nillable parameters, the binding doesn't work well. For example the pi element of the soap message is bound to pj web method parameter. To make the service work, i have to use all the parameters in my soap request even if most of them have an empty value. It is very strange. I don't know if i am clear enough but i hope that you will help me. -- View this message in context: http://www.nabble.com/Soap-request-issue-when-a-parameter-is-null-tp18771917p18771917.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Keith Chapman Senior Software Engineer WSO2 Inc. Oxygenating the Web Service Platform. http://wso2.org/ blog: http://www.keith-chapman.org -- View this message in context: http://www.nabble.com/Soap-request-issue-when-a-parameter-is-null-tp18771917p18772504.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
