You are viewing a plain text version of this content. The canonical link for it is here.

Posted to java-user@axis.apache.org by "Patel, Ronak (US SSA)" <ro...@baesystems.com> on 2007/08/01 21:05:40 UTC

Different binding in auto generated wsdl (soap11, soap12, http)

Expanding on Orly Lampert's email from October 2006, I created a wsdl
with one binding (soap1 binding) and one port with that
binding.
 
When I view the wsdl which is generated by axis (?wsdl) I always get 3
bindings and 3 ports added by axis2 (soap11, soap12 and http). 
 
Now, I want to keep only the SOAP11 port and force Axis to use the Port
Name that I specify in the WSDL file.
 
Without this in place, there is no way a client written using the
original WSDL can work with this service.
 
Can anyone help me? I can't seem to find anything on this on the web.
 
Ronak Patel
Software Engineer
BAE Systems S2

Re: Different binding in auto generated wsdl (soap11, soap12, http)

Posted by keith chapman <ke...@gmail.com>.

Hi Patel,

You can set this parameter in the servoces.xml. Also pack your original wsdl
in to the meta-inf directory of the aar file.

<parameter name="useOriginalwsdl">true</parameter>

This will forse Axis2 to use your original WSDL. BTW wat is your Axis2
version?

Thanks,
Keith.

On 8/2/07, Patel, Ronak (US SSA) <ro...@baesystems.com> wrote:
>
>  Expanding on Orly Lampert's email from October 2006, I created a wsdl with one binding (soap1 binding) and one port with that
>
> binding.
>
>
>
> When I view the wsdl which is generated by axis (?wsdl) I always get 3
>
> bindings and 3 ports added by axis2 (soap11, soap12 and http).
>
>
>
> Now, I want to keep only the SOAP11 port and force Axis to use the Port Name that I specify in the WSDL file.
>
>
>
> Without this in place, there is no way a client written using the original WSDL can work with this service.
>
>
>
> Can anyone help me? I can't seem to find anything on this on the web.
>
>
>
> Ronak Patel
>
> Software Engineer
>
> BAE Systems S2
>
>
>



-- 
Keith Chapman
WSO2 Inc.
Oxygen for Web Services Developers.
http://wso2.org/

RE: xs:anyType deserialize problem in Axis2 version 1.2

Posted by Ken Tam <ke...@proteustech.com>.

Hi Deepal,

Is this a known issue? Currently, a null is returned without any error even
when there is a value in the SOAP response.

I was able to workaround this problem by using my own version of the
beanutil.deserialize() method.

Thanks,
Ken

-----Original Message-----
From: Deepal jayasinghe [mailto:deepalk@gmail.com]
Sent: Friday, August 03, 2007 12:09 AM
To: axis-user@ws.apache.org
Subject: Re: xs:anyType deserialize problem in Axis2 version 1.2


Ken Tam wrote:
> Hi all,
>
> I've exposed a POJO web service with a method which returns another
> POJO containing a member of type Object. This translates to xs:anyType
> in the WSDL. I wrote an AXIS2 client to consume this web service. The
> value of the Object is null after the deserialization process. The
> actual value of the Object member is a simple type (String, Float and
> Integer). Is there another way to instruct the WSDL generation process
> to use a different value? Is this a deserialization issue?
At the moment there is no way to configure that.

Thanks
Deepal

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org

Re: xs:anyType deserialize problem in Axis2 version 1.2

Posted by Deepal jayasinghe <de...@gmail.com>.

Ken Tam wrote:
> Hi all,
>  
> I've exposed a POJO web service with a method which returns another
> POJO containing a member of type Object. This translates to xs:anyType
> in the WSDL. I wrote an AXIS2 client to consume this web service. The
> value of the Object is null after the deserialization process. The
> actual value of the Object member is a simple type (String, Float and
> Integer). Is there another way to instruct the WSDL generation process
> to use a different value? Is this a deserialization issue?
At the moment there is no way to configure that.

Thanks
Deepal

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org

xs:anyType deserialize problem in Axis2 version 1.2

Posted by Ken Tam <ke...@proteustech.com>.

Hi all,

I've exposed a POJO web service with a method which returns another POJO
containing a member of type Object. This translates to xs:anyType in the
WSDL. I wrote an AXIS2 client to consume this web service. The value of the
Object is null after the deserialization process. The actual value of the
Object member is a simple type (String, Float and Integer). Is there another
way to instruct the WSDL generation process to use a different value? Is
this a deserialization issue?

Thanks,
Ken