Axis2 does not support soap encoding currently. I have done it half way.
Sometimes I may be
able to finish it for Axis2 1.4.
thanks,
Amila.
On Wed, Mar 5, 2008 at 7:37 AM, Eric Chow [EMAIL PROTECTED] wrote:
Hi,
I tried to use Axis-1.4 and successfully generate the stub but it
throws another
My guess is that Axis is not picking up the right jars. Please verify
that you've set up your classpath properly and the Axis jars are firs
in line.
Anne
On Tue, Mar 4, 2008 at 10:07 PM, Eric Chow [EMAIL PROTECTED] wrote:
Hi,
I tried to use Axis-1.4 and successfully generate the stub but it
Hello,
I have a WSDL from service provider, it throws the following exception
when I use WSDL2JAVA to generate stub:
[java] - Encoded use is not supported
[java]
org.apache.axis2.description.WSDL11ToAxisServiceBuilder$WSDLProcessingException:
Encoded use is not supported
[java]
i think you have to use axis 1.4
On Tue, Mar 4, 2008 at 8:53 PM, Eric Chow [EMAIL PROTECTED] wrote:
Hello,
I have a WSDL from service provider, it throws the following exception
when I use WSDL2JAVA to generate stub:
[java] - Encoded use is not supported
[java]
Hi,
I tried to use Axis-1.4 and successfully generate the stub but it
throws another exception when running the code:
Exception in thread main java.lang.NoSuchMethodError:
org.apache.axis.description.OperationDesc.setStyle(Lorg/apache/axis/constants/Style;)V
at
It means, use Axis1 as you cannot use Axis2.
On 5/21/07, wolverine my [EMAIL PROTECTED] wrote:
Hi!
In my case the WSDL is provided by the service provider which I'm not
allowed to make changes.
Does this also means that I should not use Axis?
On 5/6/07, stefan_dragnev [EMAIL PROTECTED]
Hi!
In my case the WSDL is provided by the service provider which I'm not
allowed to make changes.
Does this also means that I should not use Axis?
On 5/6/07, stefan_dragnev [EMAIL PROTECTED] wrote:
Anne,
Thanks a lot for your help. Your explanations were really helpful.
I've already
Stefan,
There were a number of reasons why the Axis2 team decided not to
implement support for SOAP encoding:
1- it's prohibited by WS-I Basic Profile
2- SOAP encoding is an optional feature in SOAP 1.2
3- It would have been a ton of work to implement support for a feature
that is being
Dims,
It is a service which currently runs on BEA Weblogic but we are migrating to
open source. The plan was to
migrate it to Axis2. Since Axis2 v1.1.1 was not throwing exceptions I was
able to generate skeleton and stub files using WSDL with rpc/encoded
bindings. Then I wrote, compiled and
Stefan,
Thanks for the summary. Regarding Axis2 v1.1.1, even though wsdl2java
did not complain, the current client would have failed to interop with
the generated service. Since the server-side code does not really
support rpc/encoded. That's exactly the reason why we throw the
exception in
Dims,
Thanks for the suggestion to use ADB and answering all my other questions.
I already read in AIXS2 documentation that ADB is the most stable and the
preferred
data binding for Axis2. The reason I decided to stick with XMLBeans is the
current codebase which I have to port to Axis2 contains
Anne,
Thanks a lot for your help. Your explanations were really helpful.
I've already switched the style to rpc/literal and removed the encoding
attribute,
but before reading your message I have missed to remove the soap encoded
parts
from the types part of the WSDL file. Now I can successfully
Amila,
No. Let's leave it as-is.
thanks,
dims
On 5/4/07, Amila Suriarachchi [EMAIL PROTECTED] wrote:
if you have put that into production, that means for the services it does
not use the encoding
work fine. So what we can do in Axis2 is to proceed by giving a waring
message as in earlier.
I have the same problem as wolverine my and was wondering what is the reason
for rpc/encoded no longer being supported in axis2 version 1.2. Is there a
document which describes what WSDL features are supported by wsdl2java tool
in axis2 1.1.1 and axis2. 1.2. If there is such document I will
Stefan,
It was not supported even in earlier versions of Axis2..we were just
not throwing exceptions properly.
-- dims
On 5/3/07, stefan_dragnev [EMAIL PROTECTED] wrote:
I have the same problem as wolverine my and was wondering what is the reason
for rpc/encoded no longer being supported in
Dims,
I'm sure the wsdl uses rpc/encoded because it contains the following
section:
binding name=WebServiceSoap type=s0:WebServiceSoap
soap:binding transport=http://schemas.xmlsoap.org/soap/http;
style=document/
operation name=UpdateCategoriesReq
soap:operation
if you have put that into production, that means for the services it does
not use the encoding
work fine. So what we can do in Axis2 is to proceed by giving a waring
message as in earlier.
Shall we do it giving only an warning message?
amila.
On 5/4/07, Davanum Srinivas [EMAIL PROTECTED]
I believe we are throwing better exceptions now...if you post the wsdl
in a bug report, we can take a look to confirm that it is indeed an
rpc/encoded wsdl which we don't support.
thanks,
dims
On 5/1/07, wolverine my [EMAIL PROTECTED] wrote:
Hi!
I encounter the following error when tried to
Hi!
I encounter the following error when tried to generate web service
client using Axis2 1.2 and XMLBeans:
WSDL2Java -uri Dummy.wsdl -p com.test.dummy -d xmlbeans -s
Using AXIS2_HOME: C:\axis2-1.2
Using JAVA_HOME:C:\Program Files\Java\jdk1.5.0_11
May 2, 2007 11:37:18 AM
19 matches
Mail list logo
