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 (JIRA)" <de...@tuscany.apache.org> on 2008/08/24 12:37:44 UTC

[jira] Reopened: (TUSCANY-2531) Problems with generated wsdl when using non service package.

     [ https://issues.apache.org/jira/browse/TUSCANY-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dave Sowerby reopened TUSCANY-2531:
-----------------------------------


I've retested this issue using 1.3.1 RC1, the changes to the WSDL now can be successfully imported by wsimport, however using wsdl2java I still see an error, which has slightly changed:

Type wsServicePOJO is referenced but not defined.

> Problems with generated wsdl when using non service package.
> ------------------------------------------------------------
>
>                 Key: TUSCANY-2531
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-2531
>             Project: Tuscany
>          Issue Type: Bug
>    Affects Versions: Java-SCA-1.3
>         Environment: Windows Weblogic 9.2 and Websphere 6.1
>            Reporter: Dave Sowerby
>            Assignee: Simon Nash
>             Fix For: Java-SCA-1.3.1
>
>         Attachments: ws.zip
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.