You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by Dave Sowerby <da...@gmail.com> on 2008/08/06 10:20:35 UTC

Problems with generated wsdl from Tuscany 1.3

Hey All,

I'm using wsdl2java to generate a proxy to a Tuscany webservice - this
is working well in most cases, however I've found a situation where it
does not....

When I have defined a parameter to an operation which does not reside
in the same package as the service itself, then the wsdl generated
does not respect the appropriate namespace required for such clients
to be able to process the wsdl appropriately.

I've attached an example scenario which demonstrates this:

o ws-common and ws-webapp being the service which generates the wsdl
through ?wsdl
o ws-client uses the axistools-maven-plugin:wsdl2java goal to process the wsdl

So the client fails with the following error:

Embedded error: WSDL2Java execution failed
Type {http://vo.ws.example.com/}WSServicePOJO is referenced but not defined.

Should I raise a jira issue for this?

Cheers,

Dave.

--
Dave Sowerby MEng MBCS

Re: Problems with generated wsdl from Tuscany 1.3

Posted by Dave Sowerby <da...@gmail.com>.
Ok, TUSCANY-2531created.

Dave.

--
Dave Sowerby MEng MBCS



On Wed, Aug 6, 2008 at 10:40 AM, Simon Nash <na...@apache.org> wrote:
> Dave Sowerby wrote:
>>
>> Hey All,
>>
>> I'm using wsdl2java to generate a proxy to a Tuscany webservice - this
>> is working well in most cases, however I've found a situation where it
>> does not....
>>
>> When I have defined a parameter to an operation which does not reside
>> in the same package as the service itself, then the wsdl generated
>> does not respect the appropriate namespace required for such clients
>> to be able to process the wsdl appropriately.
>>
>> I've attached an example scenario which demonstrates this:
>>
>> o ws-common and ws-webapp being the service which generates the wsdl
>> through ?wsdl
>> o ws-client uses the axistools-maven-plugin:wsdl2java goal to process the
>> wsdl
>>
>> So the client fails with the following error:
>>
>> Embedded error: WSDL2Java execution failed
>> Type {http://vo.ws.example.com/}WSServicePOJO is referenced but not
>> defined.
>>
>> Should I raise a jira issue for this?
>>
> I don't see any attachment in your email.  It looks like it was stripped
> by the mailing list.  Please raise a JIRA issue and attach the test case
> there so that I can reproduce the problem.  Thanks.
>
>  Simon
>
>> Cheers,
>>
>> Dave.
>>
>> --
>> Dave Sowerby MEng MBCS
>
>

Re: Problems with generated wsdl from Tuscany 1.3

Posted by Simon Nash <na...@apache.org>.
Dave Sowerby wrote:
> Hey All,
> 
> I'm using wsdl2java to generate a proxy to a Tuscany webservice - this
> is working well in most cases, however I've found a situation where it
> does not....
> 
> When I have defined a parameter to an operation which does not reside
> in the same package as the service itself, then the wsdl generated
> does not respect the appropriate namespace required for such clients
> to be able to process the wsdl appropriately.
> 
> I've attached an example scenario which demonstrates this:
> 
> o ws-common and ws-webapp being the service which generates the wsdl
> through ?wsdl
> o ws-client uses the axistools-maven-plugin:wsdl2java goal to process the wsdl
> 
> So the client fails with the following error:
> 
> Embedded error: WSDL2Java execution failed
> Type {http://vo.ws.example.com/}WSServicePOJO is referenced but not defined.
> 
> Should I raise a jira issue for this?
> 
I don't see any attachment in your email.  It looks like it was stripped
by the mailing list.  Please raise a JIRA issue and attach the test case
there so that I can reproduce the problem.  Thanks.

   Simon

> Cheers,
> 
> Dave.
> 
> --
> Dave Sowerby MEng MBCS