[
http://issues.apache.org/jira/browse/TUSCANY-120?page=comments#action_12413839
]
Venkatakrishnan commented on TUSCANY-120:
-----------------------------------------
Hi Raymond... Here is what I understand from the code in the attached zipfile
- There is a service interface org.soapinterop.CreditScoreDocLit that has a
method that uses two statically typed SDOs: -
- org.example.creditscore.doclit.Customer (as an argument)
- org.example.creditscore.doclit.CreditReport (as return type)
- The output in test1.xsd seem to have been generated for this interface and
the SDO types used in it.
I tried the Java2WSDL tool for this interface and her is the schema definition
that I got as output: -
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema";
xmlns:stn_1="http://doclit.creditscore.example.org/xsd";
targetNamespace="http://doclit.creditscore.example.org/xsd";
elementFormDefault="unqualified"
attributeFormDefault="unqualified">
<xs:element type="stn_1:Customer" name="Customer" />
<xs:complexType name="Customer">
<xs:sequence>
<xs:element type="xs:string" name="ssn" />
<xs:element type="xs:string" name="firstName" />
<xs:element type="xs:string" name="lastName" />
</xs:sequence>
</xs:complexType>
<xs:element type="stn_1:CreditReport" name="CreditReport" />
<xs:complexType name="CreditReport">
<xs:sequence>
<xs:element type="xs:int" name="score" />
</xs:sequence>
</xs:complexType>
</xs:schema>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema";
xmlns:ns="http://soapinterop.org/xsd";
xmlns:stn_3="http://doclit.creditscore.example.org/xsd";
targetNamespace="http://soapinterop.org/xsd";
elementFormDefault="unqualified" attributeFormDefault="unqualified">
<xs:import namespace="http://doclit.creditscore.example.org/xsd"; />
<xs:element name="getCreditScore">
<xs:complexType>
<xs:sequence>
<xs:element type="stn_3:Customer" name="param0" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="getCreditScoreResponse">
<xs:complexType>
<xs:sequence>
<xs:element type="stn_3:CreditReport" name="return" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
Questions
--------------
1) Comparing this with the output in test1.xsd, I understand that there are a
few attributes missing in the schema element, that relate to ecore. Also for
every SDO type there is an instance class attribute that points back to the
java class name of the SDO. Must this be fixed? Can we do this as part of the
Java2WSDL tool itself?
2) With reference to the output pasted above can you please point out the
namespace related inconsistencies? i.e. what you see there against what you
actually expect to be there.
3) My approach to this is that for this generation we should continue to use
the sca-tools i.e. Java2WSDL. We might extend it to handle things that are not
supported as of now say for the case of SDO types. But then, at the end of it
we will have this one tool to do generate XSDs and WSDL from Java. Is this a
right line of thought or are there other considerations that will necessitate
the development of another tool like the Java2XSDGenerator ?
> 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: java2wsdl-codegen.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]
