Hi Anthony,
Hm... i was thinking - wouldn't it be possible to just modify (or
create a new ) XLS template for Axis2 databinding extension. As far as
I see, the emitter instance takes the template and the generated XML
model from memory and emits out code (stubs, skeletons,
MessageReceiver whatever). Since SDO is transparent to the actual Java
<-> XML mapping, we can take any of the JiBX, JAXB, XMLBeans or ADB
extensions, and use their Extension and Codegen Utility classes, and
just modify the XLS template (i.e fromOM(..), toOM(..), etc. parts).
Of course, this also assumes that we are bound to the above binding
framework's XSD support, in case some provider has written their own
SDO XML binding.
What do you think ?
Regards,
Angel
On 1/9/07, ant elder (JIRA) <[email protected]> wrote:
SDO databinding for Axis2
-------------------------
Key: TUSCANY-1038
URL: https://issues.apache.org/jira/browse/TUSCANY-1038
Project: Tuscany
Issue Type: New Feature
Components: Java SDO Implementation
Affects Versions: Java-SDO-Mx
Reporter: ant elder
Fix For: Java-SDO-Mx
Implement a native Axis2 databinding for SDO.
Axis2 supports pluggable databindings and currently has support for things like
xmlbeans, jibx, and Axis2s own ADB. It would help promote SDO if we implemented
an Axis2 databinding for SDO.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]