This JIRA issue brings up some interesting issues when dealing with top down approach, which is failing, in this particular case because the WSDL in use has a doc-little wrap style, and the interface generated is unwrapped. This scenario works by removing the interface.wsdl and just using the generated java interface as the service contract without any modifications on the Atom binding implementation.
After spending several hours on this, here is what I have found : a) Using the "wrapper style" interface.wsdl shields the databinding framework from using the java interface to do data transformation. b) How do we normalize the no schema based data (which can be just a piece of the URI or a query string in REST style bindings such as the Atom binding) into some XML format... and how to deal with wrapping/unwrapping the data based on the design of the target interface. Also, the To better work on this, I would like to better understand the use-case scenario and where the requirement to use a WSDL interface is coming from. Is this intended to be used with a WSDL friendly component (e.g BPEL) ? Thoughts ? [1] https://issues.apache.org/jira/browse/TUSCANY-3166 -- Luciano Resende Apache Tuscany, Apache PhotArk http://people.apache.org/~lresende http://lresende.blogspot.com/
