Hi, Pradeep. I hereby bring the conversation to the Tuscany mailing list.
Please see my comments below. Thanks, Raymond From: Pradeep Fernando Sent: Saturday, May 09, 2009 7:52 AM To: Raymond Feng Subject: Re: Tuscany-WSDL2Java hi raymond, comments inline. I assume you only have to plug in the databinding parts into the CXF code. If so, we can reference the CXF code as external maven dependencies. i thought its better to have tuscany specific codegen tools based on CXF one. i mean there can be tuscany specific requirements such as wsdl s having only portType. may be we will be able to make a lightweight tool by removing some CXF specific requirements in the tool(still cant give you a concrete example.) anyway you knw the tuscany requirements better than i do. so lets do it in the way you suggested. <rfeng> 1) We need to have the right balance here such as: a. Keep the CXF dependencies to a minimal set b. Avoid duplicating the CXF code 2) The Tuscany wsdl2java requirements are two parts: a. Generate java interfaces (not implementation classes) from the WSDL (it may only contain the portType, or portType + binding, or portType+binding+service/port. IIRC, the CXF tool supports all cases). b. Generate parameter/return/fault types using pluggable databindings in addition to JAXB. At this point, SDO databinding is desired to have. I think you should really focus on adding the databinding support as CXF probably has covered a. </rfeng> Are you familiar with maven? I was asking you to create a maven project which contains the JUNIT test case to show the programmatic way to generate java code out of a WSDL document. i'm not a guru.But can do work after bit of googling. I created a maven module requested by you. I wrote it as a independent module.got the dependecy list by running the mvn dependency:tree in the CXF module. then added some more databinding & frontend related dependencies. Think this is what you asked. you may want this as a module in tuscany code so we can check in as the first step (by supplying a patch). if it is the case i can modify this. please suggest name for the module if it is the case since i found wsdltojava module in tuscany code base. for the time being i have hosted the code in google-code. note that this is not the code to be check in.(no apache license headers.) <rfeng>I STRONGLY recommend you work with Tuscany code base directly. Having a 3rd party repo only adds one more layer of complexity. If you want to keep local changes, you should try a tool like GIT.<rfeng> svn co http://tuscany-wsdl2java-soc2009.googlecode.com/svn/trunk/mavenModule plz give your suggestions & coments on the code, <rfeng>The module looks like a good starting point. Maybe we should use a test-driven approach here. basically, add a few WSDLs with different styles and have the test case to run the wsdl2java tool.<rfeng> that sand box thing is great. I was looking for that sort of thing. So can i check in code to that sand box area? <rfeng>You cannot check in code until you gain the committer status from the project. Please start to contribute what you have done as patches. Typically, you check out the tuscany code from svn, making changes, and then run svn diff to create a patch. You should run svn add command to add new files under version control before creating the patch.</rfeng> thanks.
