[ http://issues.apache.org/jira/browse/TUSCANY-120?page=all ]
Venkatakrishnan updated TUSCANY-120:
------------------------------------
Attachment: Tuscany-Java2WSDL-SDO-Jun-29.diff
Hi Jean / Raymond / Frank / Ant,
Here is an update to the Java2WSDL Tool in Tuscany. Here is what this
update does.
- Handles the case when service methods have SDOs for arguments and retrun types
- Provides a fix for the issue raised in Axis2-756
- Has testcases that demonstrate handling of SDO Types and Axis2-756.
IMPORTANT
----------------
- The SDO2XSD generation is not complete. For example if I take sequences.xsd
and generate the schema type defns. the output is not comparable. I have
followed most of what is in the specs to map the generated SDOs to XSDs. But
then there are some ambiguities or lack of information in the generated SDOs to
be able to generate the XSDs more accurately.
- This could be a limitation as in the generated SDOs also simply follow what
the specs metion for XSD 2 SDO mapping. So we might have to update the specs
first and then the code generation.
- Alternatively we could augment the generated SDOs with annotations which can
be used during the SDO2XSD generation phase
What I have put in place is the basic mechanism and framework to generate XSDs
from SDO types. From now on it is only a matter of adding handlers for various
mapping rules as we evolve them in the specs or in the generated SDOs.
Now, if we are going to fix this from the SDO Impl standpoint, then can I start
raising JIRA issues for the incompatibilities that I am observing. Please
advise.
Thanks.
> Axis2 WS binding support for entryPoint without pre-existing WSDL
> ------------------------------------------------------------------
>
> Key: TUSCANY-120
> URL: http://issues.apache.org/jira/browse/TUSCANY-120
> Project: Tuscany
> Type: Bug
> Components: Java SCA Axis Binding
> Versions: Java-Mx
> Reporter: ant elder
> Assignee: Raymond Feng
> Fix For: Java-Mx
> Attachments: Tuscany-Java2WSDL-SDO-Jun-29.diff, java2wsdl-codegen.zip,
> xsdgen.zip
>
> Where the entryPoint doesn't use interface.wsdl then the pre-existing WSDL
> document shouldn't be required. Axis2 can generate WSDL at runtime based on
> the service interface so the Axis2 binding can use that to support the
> following:
> <entryPoint name="AccountService">
> <interface.java
> interface="org.apache.tuscany.binding.axis2.assembly.tests.bigbank.account.services.account.AccountService"/>
> <binding.ws/>
> <reference>AccountServiceComponent</reference>
> </entryPoint>
> See ML discussion:
> http://mail-archives.apache.org/mod_mbox/ws-tuscany-dev/200603.mbox/[EMAIL
> PROTECTED]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
