Hi,

To improve the Tuscany databinding framework for simplicity and flexibility, I come out a list of potential TODOs. Your feedback/ideas/help will be very welcome.

* Refine/simplify the databinding SPIs (for better extensibility and consumeablity) * Make the databinding framework easy to use as a utility in addtion to an interceptor (Ideally, other projects can leverage this framework without pulling into the whole tuscany runtime. I think we are very close.) * Use MIME types to model the databinding ids (for example, application/xml, application/x-java-serialized-object, image/jpeg) * Support MIME based binary data types (incuding the xmime extensions in WSDL/XSD) * Improve the performance of key transformers (such as JAXB <--> AXIOM, we could reuse some JAXB code from Axis2 JAXWS support) * Better support for collective/aggregate data types such as java.util.Collection * Support annotations of a java type (for example, an InputStream can be used to contain different formats of data) to further constrain the data type (We could use the JAXB annotation for this purpose) * Find better ways to represent the databinding requirements for bindings which weakly-typed message structure (no well-defined wire format) such as JMS Message or JCA Record
* More and better documents

Thanks,
Raymond

Reply via email to