Re: axis2 status of rpc encoding

2008-02-21 Thread John Langley
Thank you for your reply Martin, 

I'm digging into the problem more now. The offending service is defined
by some wsdl that is complex enough to potentially obscure the problem.
I will try and recreate the problem with a simple example and forward on
the results as I get them. 

Thanks again for the reply! It helps to know that there is sample / test
code that I can dig into. One of the things I will probably do is
recreate the axis2 test but implement it with the service side being
built and delivered with axis1 tools. 

-- Langley 



On Wed, 2008-02-20 at 09:44 -0500, Martin Gainty wrote:
 Hi John
 
 2 questions:
 1)Cant help without looking at the wsdl for a service with a pingReturn
 operation
 2)rpc is supported as exemplified style=rpc attribute illustrated in
 intergration/test-resources/rpc/test-rpc-2.wsdl
  binding name=echoBinding type=y:echoPortType
 soap:binding style=rpc
 transport=http://schemas.xmlsoap.org/soap/http/
 operation name=echo
 soap:operation soapAction=echo/
 input
 soap:body use=literal/
 /input
 output
 soap:body use=literal/
 /output
 /operation
 /binding
 
 HTH
 Martin--
 978-400-7544
 
 - Original Message -
 From: John Langley [EMAIL PROTECTED]
 To: axis-user@ws.apache.org
 Sent: Wednesday, February 20, 2008 8:43 AM
 Subject: axis2 status of rpc encoding
 
 
  Hi,
I've been trying to use Axis2 to generate java classes (using
  wsdl2java.sh) from wsdl for that describes an rpc/literal service
  delivered from Axis1. Regardless of which options I choose I seem to
  consistently get a complaint about an unexpected subelement.
 
  org.apache.axis2.databinding.ADBException: Unexpected subelement
  pingReturn
  org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException:
  Unexpected subelement pingReturn
 
 
What is the official status of rpc encoding support in Axis2? I've
  seen Jira issues that have a status of resolved around this, but I see
  comments on the user mailing list suggesting that axis2 does not support
  rpc encoding.
 
  Can anyone comment on either: 1) the official status of rpc encoding
  support or 2) their personal experience with it?
 
  Thanks in advance
 
  -- Langley
 
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: axis2 status of rpc encoding

2008-02-21 Thread Amila Suriarachchi
I started adding rpc/encoding some times ago and there are some suggestions
for that. I have to finish it.
The current status is not completed. Most probably this will available with
Axis2 1.4 release.

Please create a jira with your wsdl.

thanks,
Amila.

On Thu, Feb 21, 2008 at 6:45 PM, John Langley [EMAIL PROTECTED]
wrote:

 Thank you for your reply Martin,

 I'm digging into the problem more now. The offending service is defined
 by some wsdl that is complex enough to potentially obscure the problem.
 I will try and recreate the problem with a simple example and forward on
 the results as I get them.

 Thanks again for the reply! It helps to know that there is sample / test
 code that I can dig into. One of the things I will probably do is
 recreate the axis2 test but implement it with the service side being
 built and delivered with axis1 tools.

 -- Langley



 On Wed, 2008-02-20 at 09:44 -0500, Martin Gainty wrote:
  Hi John
 
  2 questions:
  1)Cant help without looking at the wsdl for a service with a pingReturn
  operation
  2)rpc is supported as exemplified style=rpc attribute illustrated in
  intergration/test-resources/rpc/test-rpc-2.wsdl
   binding name=echoBinding type=y:echoPortType
  soap:binding style=rpc
  transport=http://schemas.xmlsoap.org/soap/http/
  operation name=echo
  soap:operation soapAction=echo/
  input
  soap:body use=literal/
  /input
  output
  soap:body use=literal/
  /output
  /operation
  /binding
 
  HTH
  Martin--
  978-400-7544
 
  - Original Message -
  From: John Langley [EMAIL PROTECTED]
  To: axis-user@ws.apache.org
  Sent: Wednesday, February 20, 2008 8:43 AM
  Subject: axis2 status of rpc encoding
 
 
   Hi,
 I've been trying to use Axis2 to generate java classes (using
   wsdl2java.sh) from wsdl for that describes an rpc/literal service
   delivered from Axis1. Regardless of which options I choose I seem to
   consistently get a complaint about an unexpected subelement.
  
   org.apache.axis2.databinding.ADBException: Unexpected subelement
   pingReturn
   org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException:
   Unexpected subelement pingReturn
  
  
 What is the official status of rpc encoding support in Axis2? I've
   seen Jira issues that have a status of resolved around this, but I
 see
   comments on the user mailing list suggesting that axis2 does not
 support
   rpc encoding.
  
   Can anyone comment on either: 1) the official status of rpc encoding
   support or 2) their personal experience with it?
  
   Thanks in advance
  
   -- Langley
  
  
   -
   To unsubscribe, e-mail: [EMAIL PROTECTED]
   For additional commands, e-mail: [EMAIL PROTECTED]
  
  
 
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




-- 
Amila Suriarachchi,
WSO2 Inc.


axis2 status of rpc encoding

2008-02-20 Thread John Langley
Hi, 
  I've been trying to use Axis2 to generate java classes (using
wsdl2java.sh) from wsdl for that describes an rpc/literal service
delivered from Axis1. Regardless of which options I choose I seem to
consistently get a complaint about an unexpected subelement. 

org.apache.axis2.databinding.ADBException: Unexpected subelement
pingReturn
org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException:
Unexpected subelement pingReturn


  What is the official status of rpc encoding support in Axis2? I've
seen Jira issues that have a status of resolved around this, but I see
comments on the user mailing list suggesting that axis2 does not support
rpc encoding. 

Can anyone comment on either: 1) the official status of rpc encoding
support or 2) their personal experience with it? 

Thanks in advance

-- Langley 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: axis2 status of rpc encoding

2008-02-20 Thread Martin Gainty
Hi John

2 questions:
1)Cant help without looking at the wsdl for a service with a pingReturn
operation
2)rpc is supported as exemplified style=rpc attribute illustrated in
intergration/test-resources/rpc/test-rpc-2.wsdl
 binding name=echoBinding type=y:echoPortType
soap:binding style=rpc
transport=http://schemas.xmlsoap.org/soap/http/
operation name=echo
soap:operation soapAction=echo/
input
soap:body use=literal/
/input
output
soap:body use=literal/
/output
/operation
/binding

HTH
Martin--
978-400-7544

- Original Message -
From: John Langley [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Sent: Wednesday, February 20, 2008 8:43 AM
Subject: axis2 status of rpc encoding


 Hi,
   I've been trying to use Axis2 to generate java classes (using
 wsdl2java.sh) from wsdl for that describes an rpc/literal service
 delivered from Axis1. Regardless of which options I choose I seem to
 consistently get a complaint about an unexpected subelement.

 org.apache.axis2.databinding.ADBException: Unexpected subelement
 pingReturn
 org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException:
 Unexpected subelement pingReturn


   What is the official status of rpc encoding support in Axis2? I've
 seen Jira issues that have a status of resolved around this, but I see
 comments on the user mailing list suggesting that axis2 does not support
 rpc encoding.

 Can anyone comment on either: 1) the official status of rpc encoding
 support or 2) their personal experience with it?

 Thanks in advance

 -- Langley


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]