I recently made some changes (going into JiBX RC1) to support using JiBX with SOAP. These are primarily designed around what I've found was necessary for JibxSoap, but I'm also planning to hook into Axis2 and the same requirements are likely to apply there. I know the 0.9 version has XmlBeans support in place - has anything been done yet to define a general-purpose API usable with other data binding frameworks? I'm interested both in runtime support and code generation (so that there's a way for Axis to pass off a schema subset to be handled by the data binding framework, along with any appropriate customization parameters for the data binding code generation, and get back some sort of map from types to classes).

I'm also curious if anyone has considered how MTOM is going to work in combination with data binding. It seems like there'll have to be some way for the data binding framework to pass back information about the blobs to be sent as attachments, and to access the attachments when unmarshalling. In the case of JiBX I'm planning to add that in 1.1 with an internal API that allows JiBX to communicate with whatever runs the transport, then supply separate implementations of the transport interface for different usages (JibxSoap, Axis2, etc.). That aspect of MTOM has always seemed a bad smell to me, but since The Powers That Be (AKA the W3C) have decided it's the wave of the future I'll do my best to work with it.

 - Dennis

Reply via email to