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

2007-08-02 Thread Erwin Reinhoud
Hello Keith,
 
I 've been wondering about this to, where can i find documentation on how to do 
this (what param in services.xml)? I use Axis2 1.2 and would really like to 
only expose a soap 1.1 service.
 
Thanks.
 
Kind regards,
Erwin

-Oorspronkelijk bericht-
Van: keith chapman [mailto:[EMAIL PROTECTED]
Verzonden: donderdag 2 augustus 2007 6:48
Aan: axis-user@ws.apache.org
Onderwerp: Re: Different binding in auto generated wsdl (soap11, soap12, http)


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=useOriginalwsdltrue/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)   mailto:[EMAIL PROTECTED] [EMAIL 
PROTECTED] 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: Different binding in auto generated wsdl (soap11, soap12, http)

2007-08-02 Thread keith chapman
Hi Erwin,

You could use the parameter  parameter
name=useOriginalwsdltrue/parameter.

Here is a sample services.xml with this parameter.

service name=MyAxisservice
description First axis2 web service /description
messageReceivers
messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-out; class=
org.apache.axis2.rpc.receivers.RPCMessageReceiver/
/messageReceivers
parameter name=ServiceClass locked=xsd:falseMathsclass/parameter
parameter name=useOriginalwsdltrue/parameter
operation name=addnumbers

/operation
/service

Thanks,
Keith.

On 8/2/07, Erwin Reinhoud [EMAIL PROTECTED] wrote:

  Hello Keith,

 I 've been wondering about this to, where can i find documentation on how
 to do this (what param in services.xml)? I use Axis2 1.2 and would really
 like to only expose a soap 1.1 service.

 Thanks.

 Kind regards,
 Erwin

 -Oorspronkelijk bericht-
 *Van:* keith chapman [mailto:[EMAIL PROTECTED]
 *Verzonden:* donderdag 2 augustus 2007 6:48
 *Aan:* axis-user@ws.apache.org
 *Onderwerp:* Re: Different binding in auto generated wsdl (soap11, soap12,
 http)

 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=useOriginalwsdltrue/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)  [EMAIL PROTECTED] 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/




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


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

2007-08-02 Thread Erwin Reinhoud
Hello Keith,
 
Thanks, i did not know that was enough. I'll give it a try.
 
Kind regards,
Erwin
 
 

-Oorspronkelijk bericht-
Van: keith chapman [mailto:[EMAIL PROTECTED]
Verzonden: donderdag 2 augustus 2007 10:30
Aan: axis-user@ws.apache.org
Onderwerp: Re: Different binding in auto generated wsdl (soap11, soap12, http)


Hi Erwin,

You could use the parameter  parameter name=useOriginalwsdltrue/parameter.

Here is a sample services.xml with this parameter.

service name=MyAxisservice 
description First axis2 web service /description
messageReceivers
messageReceiver mep= http://www.w3.org/2004/08/wsdl/in-out  
class=org.apache.axis2.rpc.receivers.RPCMessageReceiver/
/messageReceivers
parameter name=ServiceClass locked=xsd:falseMathsclass/parameter
parameter name=useOriginalwsdltrue/parameter 
operation name=addnumbers 

/operation
/service

Thanks,
Keith.


On 8/2/07, Erwin Reinhoud  [EMAIL PROTECTED] wrote: 

Hello Keith,
 
I 've been wondering about this to, where can i find documentation on how to do 
this (what param in services.xml)? I use Axis2 1.2 and would really like to 
only expose a soap 1.1 service.
 
Thanks.
 
Kind regards,
Erwin

-Oorspronkelijk bericht-
Van: keith chapman [mailto: [EMAIL PROTECTED]
Verzonden: donderdag 2 augustus 2007 6:48
Aan: axis-user@ws.apache.org
Onderwerp: Re: Different binding in auto generated wsdl (soap11, soap12, http)


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=useOriginalwsdltrue/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)   mailto:[EMAIL PROTECTED] [EMAIL 
PROTECTED] 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/ 




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



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

2007-08-01 Thread keith chapman
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=useOriginalwsdltrue/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) [EMAIL PROTECTED] 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/