On Thursday 12 August 2010 9:46:51 am Nilupa Bandara wrote:
> Hi,
> 
> I've updated the jibx databinding code to[1] and tested the code generation
> with the attached StockQuoteService.wsdl. It generates the proper Java
> classes for the schema embedded in the WSDL, skeleton code of both client
> and the server and  proper message exchange happens when JiBX databinding
> is set without any problem. At the moment I am writing some test cases and
> javadoc comments which I'm hoping to commit in next few days.

Super cool.  Nice work.


> 
> There are couple of improvements which I would like to do
> 
> - Support '-compile' option
> 
> If the option is set, JiBX databinding should compile the generated Java
> source files and should run the jibx-binding compiler against the generated
> class files using the generated binding.xml. Since the jibx-binding
> compiler only accepts class files (not source files) I am thinking  how to
> compile the generated source files. Is there a standard way of
> programmatically compile source files in Java 5 platform.? (I found some
> web resources illustrating how to do it in Java 6, but couldn't find any
> for Java 5) If there is, then I can enhance the JiBXDatabindingTooling to
> programmatically compile the generated source files and run the
> jibx-compiler against the those class files when '-compile' option is set.

Use our Compiler class:
common/common/src/main/java/org/apache/cxf/common/util/Compiler.java

It kind of abstracts out whether it can use the Java6 tool or it has to fork 
out to javac.    


> - The implementation of getWrapperType() method in JiBXToolingDataBinding
> class looks at the only one (ValueElement) of child elements of
> BindingElement which contains binding/type information of generated
> classes. It can certainly be improved to observe other child elements
> namely StuctElement and CollectionElement when required (see [2]). I am
> looking for some schema/wsdl artifacts which will help me on that and it
> would be great if anyone can point me to such.

Well, if you want some very complex things, you could use the type test wsdl 
in testutils:
testutils/target/generated/src/main/resources/wsdl/type_test/type_test_doclit_soap.wsdl

That's probably way overkill though.   

Dan

 
> Thanks & Best Regards,
> Nilupa
> 
> 
> 
> [1] http://github.com/nilupa/cxf/tree/trunk/rt/databinding/jibx/
> [2]
> http://sourceforge.net/mailarchive/message.php?msg_name=4C5CD68B.7070200%40
> sosnoski.com

-- 
Daniel Kulp
[email protected]
http://dankulp.com/blog

Reply via email to