You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Sean Zhou (JIRA)" <tu...@ws.apache.org> on 2008/01/21 19:44:36 UTC

[jira] Created: (TUSCANY-2008) WSDL2Java to handle multi porttypes in WSDL

WSDL2Java to handle multi porttypes in WSDL
-------------------------------------------

                 Key: TUSCANY-2008
                 URL: https://issues.apache.org/jira/browse/TUSCANY-2008
             Project: Tuscany
          Issue Type: Bug
          Components: Java SCA Tools
         Environment: Windows XP
            Reporter: Sean Zhou


Three problems with WSDL2Java handling multi porttypes in WSDL:

1) WSDL2Java should not require the port info to generate Java interfaces 
for porttypes.
If a WSDL document has porttypes but no wsdl:service and wsdl:port elements, 
no Java interfaces are generated although SDO classes are generated for the 
schema. When we use a WSDL document to define an interface, it is only the 
porttype and schema definition that matters. I don't see why WSDL2Java 
requires service/port to generate Java interface for porttype.

2) All schema data types are processed even if only some ports are 
selected when running WSDL2Java.
The WSDL2JavaGenerator.generateFromWSDL() method accepts a String[] 
parameter (this parameter is not exposed on command line) that specifies 
an array of port names. WSDL2Java generates Java interfaces only for 
porttypes that used by the selected ports. While the defined scope works 
on porttypes, the whole schema is processed and SDO classes are generated 
for all data types.

3) Cannot select porttypes for code generation.
As mentioned in 1), we may care about only porttype and schema if we 
use the WSDL document for interface definition. If there are multiple 
porttypes in the WSDL document, WSDL2Java should be able to allow the 
user to select target porttypes. Currently, WSDL2Java allows to specify 
ports only.


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


---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org


[jira] Updated: (TUSCANY-2008) WSDL2Java to handle multi porttypes in WSDL

Posted by "Sean Zhou (JIRA)" <tu...@ws.apache.org>.
     [ https://issues.apache.org/jira/browse/TUSCANY-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Zhou updated TUSCANY-2008:
-------------------------------

        Fix Version/s: Java-SCA-1.1
    Affects Version/s: Java-SCA-1.0.1

> WSDL2Java to handle multi porttypes in WSDL
> -------------------------------------------
>
>                 Key: TUSCANY-2008
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-2008
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Java SCA Tools
>    Affects Versions: Java-SCA-1.0.1
>         Environment: Windows XP
>            Reporter: Sean Zhou
>             Fix For: Java-SCA-1.1
>
>
> Three problems with WSDL2Java handling multi porttypes in WSDL:
> 1) WSDL2Java should not require the port info to generate Java interfaces 
> for porttypes.
> If a WSDL document has porttypes but no wsdl:service and wsdl:port elements, 
> no Java interfaces are generated although SDO classes are generated for the 
> schema. When we use a WSDL document to define an interface, it is only the 
> porttype and schema definition that matters. I don't see why WSDL2Java 
> requires service/port to generate Java interface for porttype.
> 2) All schema data types are processed even if only some ports are 
> selected when running WSDL2Java.
> The WSDL2JavaGenerator.generateFromWSDL() method accepts a String[] 
> parameter (this parameter is not exposed on command line) that specifies 
> an array of port names. WSDL2Java generates Java interfaces only for 
> porttypes that used by the selected ports. While the defined scope works 
> on porttypes, the whole schema is processed and SDO classes are generated 
> for all data types.
> 3) Cannot select porttypes for code generation.
> As mentioned in 1), we may care about only porttype and schema if we 
> use the WSDL document for interface definition. If there are multiple 
> porttypes in the WSDL document, WSDL2Java should be able to allow the 
> user to select target porttypes. Currently, WSDL2Java allows to specify 
> ports only.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org