Created and prototyped http://issues.apache.org/jira/browse/TUSCANY-1144 to make "2-2. SDO integration" "Option -importSchema" possible.
On 2/23/07, Yang ZHONG <[EMAIL PROTECTED]> wrote:
I've tried option "-C, --importSchema" with Axis2 1.1.1, not supported (yet). As for proposed option "-importSDO", no intention to use SDO mapping (since JAXB may be the domain candidate). Static SDO is only used for its XSD info if available, such as NameSpace, element/attribute form, cardinality, default, annotation, substitution, sequence/choice, etc. which are not available from Java class. On 2/23/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote: > > I have more questions on your questions :) > > Yang ZHONG wrote: > > 2 questions on Java2WSDL. > > > > 2-1. Source path > > I use "mvn -Peclipse eclipse:eclipse" to generate .classpath for > > Eclipse. > > The source path is incomplete, therefore not only can't the project > > compile, but also does the Test Case generate empty WSDL portType. > (WSDL > > content is not checked) > > How to make this into .classpath please: > > <classpathentry kind="src" path="target/sdo-source"/> > > This usually works for me. Can you describe the steps you're following, > starting with which folder are you running mvn -Peclipse eclipse:eclipse > from? > > > > > 2-2. SDO integration > > A Java class may be a static SDO. Not only may SDO have XSD info, but > > also > > could SDO know XSD location. > > What do you think to enable all these options: > > 1. Option -importSchema: If XSD location is available, generate WSDL > to > > import that. > > Axis(2) supports option "-C, --importSchema" ( > > http://ws.apache.org/axis/java/reference.html#Java2WSDLReference) > > Do you know how this option works in the Axis2 Java2WSDL? Is there a > pointer to more info? > > The Axis2 doc says "-C a file or URL to an XML Schema that should be > physically imported into the generated WSDL", but it doesn't say: > - if this can be used to import multiple XSDs > - if "physically import" means copy the contents of the XSD or just > generate an <xsd:import> statement > - if the tool will still generate some XSD types on its own or will not > generate any XSD, assuming that the imported XSD covers all the types > that need to be generated. > > > 2. Option -importSDO: If XSD into is available, generate XSD using > > SDO and > > generate WSDL using Axis(2) to import that > > What do you mean by "generate XSD using SDO"? Are you talking about > generating an XSD from the SDO type definition, using the SDO <-> XSD > mapping rules described in the SDO spec? > > > 3. Option -inlineSDO: If XSD info is available, generate WSDL using > > Axis(2) with inline schema from SDO > > > > -- > Jean-Sebastien > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Yang ZHONG
-- Yang ZHONG
