Fuhwei, you're right.. the BP's just saying not to use WSDL import to import
schemas directly.  Sorry for the confusion.
Scott

On 6/6/07, Fuhwei Lwo (JIRA) <[email protected]> wrote:


    [
https://issues.apache.org/jira/browse/TUSCANY-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502077]

Fuhwei Lwo commented on TUSCANY-1327:
-------------------------------------

<wsdl:include> was introduced in WSDL 1.2 so for now, let's not worry
about it.

According to WS-I Basic Profile 1.0 WSDL 1.1, the users can use the
following to import their schemas. In fact, it's one of the best pratices in
the web services industry.

Bindings.wsdl  --- wsdl:import ---> Messages.wsdl --- xsd:import --->
Types.xsd

Currently, if I did codegen on Bindings.wsdl, nothing happens. If I
codegened on Messages.wsdl, it's working fine which will generate codes
from namespaces from Messages.wsdl and Types.xsd. I will attach all 3
wsdl/xsd files soon.

> Generate static SDO APIs from wsdl files with type definition from
<wsdl:import> and <wsdl:include>
>
---------------------------------------------------------------------------------------------------
>
>                 Key: TUSCANY-1327
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-1327
>             Project: Tuscany
>          Issue Type: New Feature
>          Components: Java SDO Tools
>    Affects Versions: Java-SDO-M2
>         Environment: WinXP
>            Reporter: Fuhwei Lwo
>         Attachments: Bindings.wsdl, Messages.wsdl, Types.xsd
>
>
> Today, SDO codegen tool can recognize and parse <wsdl:types> content to
generate static SDO APIs. However, it ignores <wsdl:import> and
<wsdl:include>. This means if I have types defined in other wsdl files and
they are imported or included by <wsdl:import> or <wsdl:include> elements,
they won't never get generated.

--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Reply via email to