wstools configuration

[thomas.diesler]

Here some feedback for jbossws-tools.xsd -r 1.6

1. General

1.1. The file should have a version identifier in the name

1.2. Readablility could be vastly improved by avoiding anonymous types. Use named complex types and reference them appropraitely.

1.3. Please care about better readability. Space and comments are cheap.

2. global configuration

2.1. global configuration should be at the top

2.2. override is a property that pertains to the filesystem like output dir, etc. It should not be part of the xml config. A commandline option is more appropriate

2.3. retainSourceFiles can never be false because we don't compile. This can be removed.

3. javaToWSDL

3.1 documentation is too restrictive

3.2. attribute endpointInterface is a bad name. It can also be an annotated endpoint impl class.

3.3. attribute oneWayOperations is too restrictive. In future we might have more options that are scoped on the method. Use a sequence of operation elements + a oneWay attribute

4. wsdlToJava

4.1 be consistent with naming. WSDL vs. wsdl

4.2 How do you specify the wsdlURL?

5. javaToXSD

5.1 Why do we need to configure this? Is this not part of javaToWSDL, which also defines a types namespace.

6. xsdToJava

6.1 Why do we need to configure this? Is this not part of wsdlToJava.

[anil.saldhana]

1. Will add the version information to the schema name. Honest miss.
2. Global options will be retained as before at the bottom. These options are used by advanced users and typically basic users will not have to deal with this.
3. JavaToXSD and XSDToJava is one feature of jbossws. Since I do not foresee any value in exposing this to general use, I will remove it.
4. I will go splurge on documentation as "space and comment are cheap". :-)

Sometime ago, you had mentioned that you would like to see less of command line options and more of xml configuration. Hence many of the attributes that can be input via the command line, were fed in the xml configuration. But with a good user guide and a lean/mean schema, it should satisfy majority of the users' needs.

Thanks for the feedback. Changes to the schema based on your feedback will also trigger changes to the user guide.

[anil.saldhana]

The schema file is changed based on Thomas's feedback. Ready for review.

[rajdeep_dua]

Hi is the JavatoWSDL tool in workable condition?
I saw the key methods commented out.
Where can i find the documentation for the same?
I saw a lot of issues in JIRA but couldnt make out where to start...

Also noticed that the WSDL namspace org.jboss.ws.tools.JavaToWSDL was referring to the older one where as the WSDL 2.0 namespace has changed in the spec released by w3c on Jan 6,2006

wsdl : "http://www.w3.org/2006/01/wsdl"

wsdli :"http://www.w3.org/2006/01/wsdl-instance"

wsdlx : "http://www.w3.org/2006/01/wsdl-extensions"

wrpc : "http://www.w3.org/2006/01/wsdl/rpc"

wsoap : "http://www.w3.org/2006/01/wsdl/soap"

whttp : "http://www.w3.org/2006/01/wsdl/http"