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 wolverine my <wo...@gmail.com> on 2007/05/02 05:45:31 UTC
WSDL2Java: WSDLProcessingException: Encoded use is not supported?
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
org.apache.axis2.description.WSDL11ToAxisServiceBuilder
populateService
SEVERE: org.apache.axis2.description.WSDL11ToAxisServiceBuilder$WSDLProcessingException:
Encoded use is not supported
Exception in thread "main"
org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing
WSDL
at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.<init>(CodeGenerationEngine.java:137)
at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)
at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
Caused by: org.apache.axis2.AxisFault: Encoded use is not supported
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService(WSDL11ToAxisServiceBuilder.java:298)
at org.apache.axis2.description.WSDL11ToAllAxisServicesBuilder.populateAllServices(WSDL11ToAllAxisServicesBuilder.java:100)
at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.<init>(CodeGenerationEngine.java:131)
... 2 more
Caused by: org.apache.axis2.description.WSDL11ToAxisServiceBuilder$WSDLProcessingException:
Encoded use is not supported
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.getPartsListFromSoapBody(WSDL11ToAxisServiceBuilder.java:1543)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.createSchemaForPorttype(WSDL11ToAxisServiceBuilder.java:1294)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.generateWrapperSchema(WSDL11ToAxisServiceBuilder.java:1198)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService(WSDL11ToAxisServiceBuilder.java:252)
... 4 more
However, the same command and WSDL file was working fine with Axis2 1.1.1.
Do you have any idea of what could be the problem?
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: WSDL2Java: WSDLProcessingException: Encoded use is not
supported?
Posted by stefan_dragnev <st...@yahoo.com>.
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 couple of thousands
lines of code and all of it uses XMLBeans. All this combined with I being
new
to Axis2 and having a tight deadline made XMLBeans the better choice for
now.
If time allows I will move everything to ADB later on.
Thanks,
Stefan
Davanum Srinivas wrote:
>
>>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 Axis2 1.2 so that people are not led down the garden path
>>and then get to know the limitation in the end and get frustrated.
>>
>>Yes, it's better to use rpc/lit. Just make sure the client is not on
>>.NET 1.x which does not support rpc/lit. XMLBeans is a bit slow under
>>some circumstances. But if it works for you, just stick to it.
>>Alternative is to use the ADB (which is the default data binding).
>>I'd definitely run it under Tomcat. SimpleHTTPServer is getting there
>>for production use, but i am more inclined to use tomcat for
>>production purposes. Also FYI, If you decide to switch to ADB, we'd
>>definitely back you up if you run into codegen issues or runtime
>>issues as both are under our control. XMLBeans is a separate project
>>as you know...
>>
>>thanks,
>>dims
>
> On 5/5/07, stefan_dragnev <st...@yahoo.com> wrote:
>>
>> 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 deployed a service using XMLBeans
>> binding but when I deployed on the server I kept getting faults each time
>> when I invoked the service. That's when I saw Axis 1.2 is already release
>> and thought that it might solve the problem. It didn't as with 1.2 I
>> could
>> not even generate stubs and skeletons and that is when I wrote for first
>> time to the email list.
>>
>> The WSDL which I inherited and is currently used in production is using
>> rpc/encoded style. I have no control over the client side to make them
>> change their code. But on Friday I modified the WSDL to use rpc/literal
>> style and was able to run wsdl2java on it without any problems. Hopefully
>> the client side will be willing to change their code to use rpc/literal
>> style.
>>
>> I'm using XMLbeans as data binding. What is more efficient when it comes
>> to
>> speed - running a standalone Axis2 server or running it under Tomcat? Are
>> there any advantages using one or the other?
>>
>> Thanks,
>> Stefan
>>
>>
>> Davanum Srinivas wrote:
>> >
>> >>Stefan,
>> >>
>> >>Is this an Axis2 based service in production? and you have a custom
>> wsdl?
>> >>
>> >>-- dims
>> >>
>> > On 5/3/07, stefan_dragnev <st...@yahoo.com> wrote:
>> >>
>> >> 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
>> >> soapAction="http://www.openuri.org/UpdateCategoriesReq" style="rpc"/>
>> >> <input>
>> >> <soap:body use="encoded" namespace="http://www.openuri.org/"
>> >> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
>> >> </input>
>> >> <output>
>> >> <soap:body use="encoded" namespace="http://www.openuri.org/"
>> >> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
>> >> </output>
>> >> </operation>
>> >> <operation name="BPDataReq">
>> >> <soap:operation soapAction="http://www.openuri.org/BPDataReq"
>> >> style="rpc"/>
>> >> <input>
>> >> <soap:body use="encoded" namespace="http://www.openuri.org/"
>> >> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
>> >> </input>
>> >> <output>
>> >> <soap:body use="encoded" namespace="http://www.openuri.org/"
>> >> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
>> >> </output>
>> >> </operation>
>> >> ......
>> >> </binding>
>> >>
>> >> I know that rpc/encoded is not supported in WS-I basic profile but
>> this
>> >> WSDL
>> >> was developed some time ago and is used in production so I'm not sure
>> >> whether I will be allowed to modify. If I'm allowed to modify it what
>> >> will
>> >> be the best way to do it so Axis2 1.2's wsdl2java will not throw
>> errors?
>> >>
>> >> Thanks.
>> >> Stefan
>> >>
>> >>
>> >> >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
>> >>
>> >> --
>> >> View this message in context:
>> >>
>> http://www.nabble.com/WSDL2Java%3A-WSDLProcessingException%3A-Encoded-use-is-not-supported--tf3678548.html#a10312820
>> >> Sent from the Axis - User mailing list archive at Nabble.com.
>> >>
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> >> For additional commands, e-mail: axis-user-help@ws.apache.org
>> >>
>> >>
>> >
>> >
>> > --
>> > Davanum Srinivas :: http://davanum.wordpress.com
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> > For additional commands, e-mail: axis-user-help@ws.apache.org
>> >
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/WSDL2Java%3A-WSDLProcessingException%3A-Encoded-use-is-not-supported--tf3678548.html#a10341325
>> Sent from the Axis - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>>
>
>
> --
> Davanum Srinivas :: http://davanum.wordpress.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/WSDL2Java%3A-WSDLProcessingException%3A-Encoded-use-is-not-supported--tf3678548.html#a10342010
Sent from the Axis - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: WSDL2Java: WSDLProcessingException: Encoded use is not supported?
Posted by Davanum Srinivas <da...@gmail.com>.
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 Axis2 1.2 so that people are not led down the garden path
and then get to know the limitation in the end and get frustrated.
Yes, it's better to use rpc/lit. Just make sure the client is not on
.NET 1.x which does not support rpc/lit. XMLBeans is a bit slow under
some circumstances. But if it works for you, just stick to it.
Alternative is to use the ADB (which is the default data binding).
I'd definitely run it under Tomcat. SimpleHTTPServer is getting there
for production use, but i am more inclined to use tomcat for
production purposes. Also FYI, If you decide to switch to ADB, we'd
definitely back you up if you run into codegen issues or runtime
issues as both are under our control. XMLBeans is a separate project
as you know...
thanks,
dims
On 5/5/07, stefan_dragnev <st...@yahoo.com> wrote:
>
> 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 deployed a service using XMLBeans
> binding but when I deployed on the server I kept getting faults each time
> when I invoked the service. That's when I saw Axis 1.2 is already release
> and thought that it might solve the problem. It didn't as with 1.2 I could
> not even generate stubs and skeletons and that is when I wrote for first
> time to the email list.
>
> The WSDL which I inherited and is currently used in production is using
> rpc/encoded style. I have no control over the client side to make them
> change their code. But on Friday I modified the WSDL to use rpc/literal
> style and was able to run wsdl2java on it without any problems. Hopefully
> the client side will be willing to change their code to use rpc/literal
> style.
>
> I'm using XMLbeans as data binding. What is more efficient when it comes to
> speed - running a standalone Axis2 server or running it under Tomcat? Are
> there any advantages using one or the other?
>
> Thanks,
> Stefan
>
>
> Davanum Srinivas wrote:
> >
> >>Stefan,
> >>
> >>Is this an Axis2 based service in production? and you have a custom wsdl?
> >>
> >>-- dims
> >>
> > On 5/3/07, stefan_dragnev <st...@yahoo.com> wrote:
> >>
> >> 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
> >> soapAction="http://www.openuri.org/UpdateCategoriesReq" style="rpc"/>
> >> <input>
> >> <soap:body use="encoded" namespace="http://www.openuri.org/"
> >> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
> >> </input>
> >> <output>
> >> <soap:body use="encoded" namespace="http://www.openuri.org/"
> >> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
> >> </output>
> >> </operation>
> >> <operation name="BPDataReq">
> >> <soap:operation soapAction="http://www.openuri.org/BPDataReq"
> >> style="rpc"/>
> >> <input>
> >> <soap:body use="encoded" namespace="http://www.openuri.org/"
> >> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
> >> </input>
> >> <output>
> >> <soap:body use="encoded" namespace="http://www.openuri.org/"
> >> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
> >> </output>
> >> </operation>
> >> ......
> >> </binding>
> >>
> >> I know that rpc/encoded is not supported in WS-I basic profile but this
> >> WSDL
> >> was developed some time ago and is used in production so I'm not sure
> >> whether I will be allowed to modify. If I'm allowed to modify it what
> >> will
> >> be the best way to do it so Axis2 1.2's wsdl2java will not throw errors?
> >>
> >> Thanks.
> >> Stefan
> >>
> >>
> >> >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
> >>
> >> --
> >> View this message in context:
> >> http://www.nabble.com/WSDL2Java%3A-WSDLProcessingException%3A-Encoded-use-is-not-supported--tf3678548.html#a10312820
> >> Sent from the Axis - User mailing list archive at Nabble.com.
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: axis-user-help@ws.apache.org
> >>
> >>
> >
> >
> > --
> > Davanum Srinivas :: http://davanum.wordpress.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >
> >
> >
>
> --
> View this message in context: http://www.nabble.com/WSDL2Java%3A-WSDLProcessingException%3A-Encoded-use-is-not-supported--tf3678548.html#a10341325
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Davanum Srinivas :: http://davanum.wordpress.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: WSDL2Java: WSDLProcessingException: Encoded use is not
supported?
Posted by stefan_dragnev <st...@yahoo.com>.
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 deployed a service using XMLBeans
binding but when I deployed on the server I kept getting faults each time
when I invoked the service. That's when I saw Axis 1.2 is already release
and thought that it might solve the problem. It didn't as with 1.2 I could
not even generate stubs and skeletons and that is when I wrote for first
time to the email list.
The WSDL which I inherited and is currently used in production is using
rpc/encoded style. I have no control over the client side to make them
change their code. But on Friday I modified the WSDL to use rpc/literal
style and was able to run wsdl2java on it without any problems. Hopefully
the client side will be willing to change their code to use rpc/literal
style.
I'm using XMLbeans as data binding. What is more efficient when it comes to
speed - running a standalone Axis2 server or running it under Tomcat? Are
there any advantages using one or the other?
Thanks,
Stefan
Davanum Srinivas wrote:
>
>>Stefan,
>>
>>Is this an Axis2 based service in production? and you have a custom wsdl?
>>
>>-- dims
>>
> On 5/3/07, stefan_dragnev <st...@yahoo.com> wrote:
>>
>> 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
>> soapAction="http://www.openuri.org/UpdateCategoriesReq" style="rpc"/>
>> <input>
>> <soap:body use="encoded" namespace="http://www.openuri.org/"
>> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
>> </input>
>> <output>
>> <soap:body use="encoded" namespace="http://www.openuri.org/"
>> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
>> </output>
>> </operation>
>> <operation name="BPDataReq">
>> <soap:operation soapAction="http://www.openuri.org/BPDataReq"
>> style="rpc"/>
>> <input>
>> <soap:body use="encoded" namespace="http://www.openuri.org/"
>> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
>> </input>
>> <output>
>> <soap:body use="encoded" namespace="http://www.openuri.org/"
>> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
>> </output>
>> </operation>
>> ......
>> </binding>
>>
>> I know that rpc/encoded is not supported in WS-I basic profile but this
>> WSDL
>> was developed some time ago and is used in production so I'm not sure
>> whether I will be allowed to modify. If I'm allowed to modify it what
>> will
>> be the best way to do it so Axis2 1.2's wsdl2java will not throw errors?
>>
>> Thanks.
>> Stefan
>>
>>
>> >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
>>
>> --
>> View this message in context:
>> http://www.nabble.com/WSDL2Java%3A-WSDLProcessingException%3A-Encoded-use-is-not-supported--tf3678548.html#a10312820
>> Sent from the Axis - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>>
>
>
> --
> Davanum Srinivas :: http://davanum.wordpress.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/WSDL2Java%3A-WSDLProcessingException%3A-Encoded-use-is-not-supported--tf3678548.html#a10341325
Sent from the Axis - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: WSDL2Java: WSDLProcessingException: Encoded use is not supported?
Posted by Davanum Srinivas <da...@gmail.com>.
Amila,
No. Let's leave it as-is.
thanks,
dims
On 5/4/07, Amila Suriarachchi <am...@gmail.com> 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.
>
> Shall we do it giving only an warning message?
>
> amila.
>
>
> On 5/4/07, Davanum Srinivas <da...@gmail.com> wrote:
> > Stefan,
> >
> > Is this an Axis2 based service in production? and you have a custom wsdl?
> >
> > -- dims
> >
> > On 5/3/07, stefan_dragnev <st...@yahoo.com> wrote:
> > >
> > > 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
> > > soapAction="http://www.openuri.org/UpdateCategoriesReq"
> style="rpc"/>
> > > <input>
> > > <soap:body use="encoded" namespace="http://www.openuri.org/"
> > >
> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/
> "/>
> > > </input>
> > > <output>
> > > <soap:body use="encoded" namespace="http://www.openuri.org/"
> > > encodingStyle="
> http://schemas.xmlsoap.org/soap/encoding/"/>
> > > </output>
> > > </operation>
> > > <operation name="BPDataReq">
> > > <soap:operation
> soapAction="http://www.openuri.org/BPDataReq"
> > > style="rpc"/>
> > > <input>
> > > <soap:body use="encoded" namespace=" http://www.openuri.org/"
> > >
> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
> > > </input>
> > > <output>
> > > <soap:body use="encoded" namespace="http://www.openuri.org/"
> > > encodingStyle="
> http://schemas.xmlsoap.org/soap/encoding/"/>
> > > </output>
> > > </operation>
> > > ......
> > > </binding>
> > >
> > > I know that rpc/encoded is not supported in WS-I basic profile but this
> WSDL
> > > was developed some time ago and is used in production so I'm not sure
> > > whether I will be allowed to modify. If I'm allowed to modify it what
> will
> > > be the best way to do it so Axis2 1.2's wsdl2java will not throw errors?
> > >
> > > Thanks.
> > > Stefan
> > >
> > >
> > > >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
> > >
> > > --
> > > View this message in context:
> http://www.nabble.com/WSDL2Java%3A-WSDLProcessingException%3A-Encoded-use-is-not-supported--tf3678548.html#a10312820
> > > Sent from the Axis - User mailing list archive at Nabble.com .
> > >
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail:
> axis-user-unsubscribe@ws.apache.org
> > > For additional commands, e-mail: axis-user-help@ws.apache.org
> > >
> > >
> >
> >
> > --
> > Davanum Srinivas :: http://davanum.wordpress.com
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >
> >
>
>
>
> --
> Amila Suriarachchi,
> WSO2 Inc.
--
Davanum Srinivas :: http://davanum.wordpress.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: WSDL2Java: WSDLProcessingException: Encoded use is not supported?
Posted by Amila Suriarachchi <am...@gmail.com>.
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 <da...@gmail.com> wrote:
>
> Stefan,
>
> Is this an Axis2 based service in production? and you have a custom wsdl?
>
> -- dims
>
> On 5/3/07, stefan_dragnev <st...@yahoo.com> wrote:
> >
> > 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
> > soapAction="http://www.openuri.org/UpdateCategoriesReq" style="rpc"/>
> > <input>
> > <soap:body use="encoded" namespace="http://www.openuri.org/"
> > encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
> > </input>
> > <output>
> > <soap:body use="encoded" namespace="http://www.openuri.org/"
> > encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
> > </output>
> > </operation>
> > <operation name="BPDataReq">
> > <soap:operation soapAction="http://www.openuri.org/BPDataReq"
> > style="rpc"/>
> > <input>
> > <soap:body use="encoded" namespace="http://www.openuri.org/"
> > encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
> > </input>
> > <output>
> > <soap:body use="encoded" namespace="http://www.openuri.org/"
> > encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
> > </output>
> > </operation>
> > ......
> > </binding>
> >
> > I know that rpc/encoded is not supported in WS-I basic profile but this
> WSDL
> > was developed some time ago and is used in production so I'm not sure
> > whether I will be allowed to modify. If I'm allowed to modify it what
> will
> > be the best way to do it so Axis2 1.2's wsdl2java will not throw errors?
> >
> > Thanks.
> > Stefan
> >
> >
> > >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
> >
> > --
> > View this message in context:
> http://www.nabble.com/WSDL2Java%3A-WSDLProcessingException%3A-Encoded-use-is-not-supported--tf3678548.html#a10312820
> > Sent from the Axis - User mailing list archive at Nabble.com.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >
> >
>
>
> --
> Davanum Srinivas :: http://davanum.wordpress.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Amila Suriarachchi,
WSO2 Inc.
Re: WSDL2Java: WSDLProcessingException: Encoded use is not supported?
Posted by Davanum Srinivas <da...@gmail.com>.
Stefan,
Is this an Axis2 based service in production? and you have a custom wsdl?
-- dims
On 5/3/07, stefan_dragnev <st...@yahoo.com> wrote:
>
> 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
> soapAction="http://www.openuri.org/UpdateCategoriesReq" style="rpc"/>
> <input>
> <soap:body use="encoded" namespace="http://www.openuri.org/"
> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
> </input>
> <output>
> <soap:body use="encoded" namespace="http://www.openuri.org/"
> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
> </output>
> </operation>
> <operation name="BPDataReq">
> <soap:operation soapAction="http://www.openuri.org/BPDataReq"
> style="rpc"/>
> <input>
> <soap:body use="encoded" namespace="http://www.openuri.org/"
> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
> </input>
> <output>
> <soap:body use="encoded" namespace="http://www.openuri.org/"
> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
> </output>
> </operation>
> ......
> </binding>
>
> I know that rpc/encoded is not supported in WS-I basic profile but this WSDL
> was developed some time ago and is used in production so I'm not sure
> whether I will be allowed to modify. If I'm allowed to modify it what will
> be the best way to do it so Axis2 1.2's wsdl2java will not throw errors?
>
> Thanks.
> Stefan
>
>
> >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
>
> --
> View this message in context: http://www.nabble.com/WSDL2Java%3A-WSDLProcessingException%3A-Encoded-use-is-not-supported--tf3678548.html#a10312820
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Davanum Srinivas :: http://davanum.wordpress.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: WSDL2Java: WSDLProcessingException: Encoded use is not supported?
Posted by Davanum Srinivas <da...@gmail.com>.
It means, use Axis1 as you cannot use Axis2.
On 5/21/07, wolverine my <wo...@gmail.com> 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 <st...@yahoo.com> wrote:
> >
> > 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 run wsdl2java
> > from Axis2
> > and generate skeleton and stubs.
> >
> > Stefan
> > --
> > View this message in context: http://www.nabble.com/WSDL2Java%3A-WSDLProcessingException%3A-Encoded-use-is-not-supported--tf3678548.html#a10342158
> > Sent from the Axis - User mailing list archive at Nabble.com.
> >
> >
> > ---------------------------------------------------------------------
> > 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
>
>
--
Davanum Srinivas :: http://davanum.wordpress.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: WSDL2Java: WSDLProcessingException: Encoded use is not supported?
Posted by wolverine my <wo...@gmail.com>.
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 <st...@yahoo.com> wrote:
>
> 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 run wsdl2java
> from Axis2
> and generate skeleton and stubs.
>
> Stefan
> --
> View this message in context: http://www.nabble.com/WSDL2Java%3A-WSDLProcessingException%3A-Encoded-use-is-not-supported--tf3678548.html#a10342158
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> 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: WSDL2Java: WSDLProcessingException: Encoded use is not
supported?
Posted by stefan_dragnev <st...@yahoo.com>.
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 run wsdl2java
from Axis2
and generate skeleton and stubs.
Stefan
--
View this message in context: http://www.nabble.com/WSDL2Java%3A-WSDLProcessingException%3A-Encoded-use-is-not-supported--tf3678548.html#a10342158
Sent from the Axis - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: WSDL2Java: WSDLProcessingException: Encoded use is not supported?
Posted by Anne Thomas Manes <at...@gmail.com>.
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 deprecated by the standards community.
4- There are still tons of other more useful features to be
implemented that have a higher priority.
If you need to maintain use of SOAP encoding, you should stick with Axis 1.x.
If you want to migrate to Axis2, you will have to convert the service
to either document/literal or rpc/literal.
The easier conversion is to rpc/literal, but I advise against that,
because there are still many environments that don't support it
(especially .Net 1.x). To convert to rpc/literal, simply change all
instances of use="encoded" to use="literal" and remove the
encodingStyle attribute from the bindings. You should also review all
your type definitions, and convert any soap encoding types to schema
types (e.g., type="soapenc:string" to type="xsd:string"), and convert
all soap encoding arrays to simple XSD arrays defined using
maxOccurs="unbounded".
The conversion to document/literal requires the following:
- change style="rpc" to style="document"
- change use="encoded" to use="literal"
- remove the namespace and encodingStyle attributes from the bindings
- define wrapper elements for all your input and output message
parameters. Input message elements should be given the same name as
the operation. Output message elements should be given a name in the
form of <methodName>Response. Each element should be defined as a
sequence containing elements of the types you've currently defined as
your message parts.
- remove all your current message parts and replace them with a single
message part referencing your newly defined wrapper elements.
For example:
Current message description:
<w:message name="fooMethodRequest">
<w:part name="foo1" type="s:string"/>
<w:part name="foo2" type="s:int"/>
</w:message>
Should be change to this:
<w:types>
<s:schema targetNamespace="urn:foo:types"
xmlns:ns1="urn:foo:types">
<s:element name="fooMethod">
<s:complexType>
<s:sequence>
<s:element name="foo1" type="s:string"/>
<s:element name="foo2" type="s:int"/>
</s:sequence>
</s:complexType>
</s:element>
</s:schema>
</w:types>
<w:message name="fooMethodRequest>
<w:part name="parameters" element="ns1:fooMethod"/>
</w:message>
Anne
On 5/3/07, stefan_dragnev <st...@yahoo.com> wrote:
>
> 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
> soapAction="http://www.openuri.org/UpdateCategoriesReq" style="rpc"/>
> <input>
> <soap:body use="encoded" namespace="http://www.openuri.org/"
> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
> </input>
> <output>
> <soap:body use="encoded" namespace="http://www.openuri.org/"
> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
> </output>
> </operation>
> <operation name="BPDataReq">
> <soap:operation soapAction="http://www.openuri.org/BPDataReq"
> style="rpc"/>
> <input>
> <soap:body use="encoded" namespace="http://www.openuri.org/"
> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
> </input>
> <output>
> <soap:body use="encoded" namespace="http://www.openuri.org/"
> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
> </output>
> </operation>
> ......
> </binding>
>
> I know that rpc/encoded is not supported in WS-I basic profile but this WSDL
> was developed some time ago and is used in production so I'm not sure
> whether I will be allowed to modify. If I'm allowed to modify it what will
> be the best way to do it so Axis2 1.2's wsdl2java will not throw errors?
>
> Thanks.
> Stefan
>
>
> >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
>
> --
> View this message in context: http://www.nabble.com/WSDL2Java%3A-WSDLProcessingException%3A-Encoded-use-is-not-supported--tf3678548.html#a10312820
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> 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: WSDL2Java: WSDLProcessingException: Encoded use is not
supported?
Posted by stefan_dragnev <st...@yahoo.com>.
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
soapAction="http://www.openuri.org/UpdateCategoriesReq" style="rpc"/>
<input>
<soap:body use="encoded" namespace="http://www.openuri.org/"
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</input>
<output>
<soap:body use="encoded" namespace="http://www.openuri.org/"
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</output>
</operation>
<operation name="BPDataReq">
<soap:operation soapAction="http://www.openuri.org/BPDataReq"
style="rpc"/>
<input>
<soap:body use="encoded" namespace="http://www.openuri.org/"
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</input>
<output>
<soap:body use="encoded" namespace="http://www.openuri.org/"
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</output>
</operation>
......
</binding>
I know that rpc/encoded is not supported in WS-I basic profile but this WSDL
was developed some time ago and is used in production so I'm not sure
whether I will be allowed to modify. If I'm allowed to modify it what will
be the best way to do it so Axis2 1.2's wsdl2java will not throw errors?
Thanks.
Stefan
>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
--
View this message in context: http://www.nabble.com/WSDL2Java%3A-WSDLProcessingException%3A-Encoded-use-is-not-supported--tf3678548.html#a10312820
Sent from the Axis - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: WSDL2Java: WSDLProcessingException: Encoded use is not supported?
Posted by Davanum Srinivas <da...@gmail.com>.
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 <wo...@gmail.com> wrote:
> 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
> org.apache.axis2.description.WSDL11ToAxisServiceBuilder
> populateService
> SEVERE: org.apache.axis2.description.WSDL11ToAxisServiceBuilder$WSDLProcessingException:
> Encoded use is not supported
> Exception in thread "main"
> org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing
> WSDL
> at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.<init>(CodeGenerationEngine.java:137)
> at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)
> at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
> Caused by: org.apache.axis2.AxisFault: Encoded use is not supported
> at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService(WSDL11ToAxisServiceBuilder.java:298)
> at org.apache.axis2.description.WSDL11ToAllAxisServicesBuilder.populateAllServices(WSDL11ToAllAxisServicesBuilder.java:100)
> at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.<init>(CodeGenerationEngine.java:131)
> ... 2 more
> Caused by: org.apache.axis2.description.WSDL11ToAxisServiceBuilder$WSDLProcessingException:
> Encoded use is not supported
> at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.getPartsListFromSoapBody(WSDL11ToAxisServiceBuilder.java:1543)
> at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.createSchemaForPorttype(WSDL11ToAxisServiceBuilder.java:1294)
> at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.generateWrapperSchema(WSDL11ToAxisServiceBuilder.java:1198)
> at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService(WSDL11ToAxisServiceBuilder.java:252)
> ... 4 more
>
>
> However, the same command and WSDL file was working fine with Axis2 1.1.1.
>
> Do you have any idea of what could be the problem?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Davanum Srinivas :: http://davanum.wordpress.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: WSDL2Java: WSDLProcessingException: Encoded use is not supported?
Posted by Davanum Srinivas <da...@gmail.com>.
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 <st...@yahoo.com> wrote:
>
> 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 appreciate
> it to get a link to it.
>
> Thanks,
> Stefan
> --
> View this message in context: http://www.nabble.com/WSDL2Java%3A-WSDLProcessingException%3A-Encoded-use-is-not-supported--tf3678548.html#a10305922
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Davanum Srinivas :: http://davanum.wordpress.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: WSDL2Java: WSDLProcessingException: Encoded use is not
supported?
Posted by stefan_dragnev <st...@yahoo.com>.
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 appreciate
it to get a link to it.
Thanks,
Stefan
--
View this message in context: http://www.nabble.com/WSDL2Java%3A-WSDLProcessingException%3A-Encoded-use-is-not-supported--tf3678548.html#a10305922
Sent from the Axis - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org