Hi all, I want to share my thoughts about having MTOM Serialization Policy Assertion specification implemented as a module into Axis2.
I have asked a similar question some time ago. You can see it here: http://www.mail-archive.com/[email protected]/msg43257.html Current situation in Axis2 1.4 is that there is a jar axis2-mtompolicy-1.4.jar that provides some basic (not full) implementation of MTOM Serialization Policy Assertion 1.0 (link: http://schemas.xmlsoap.org/ws/2004/09/policy/optimizedmimeserialization/optimizedmimeserialization-policy.pdf) . Meantime a working draft (WD) of the specification is in progress: MTOM Serialization Policy Assertion 1.1 (link: http://www.w3.org/TR/soap12-mtom-policy/). Here is an example of the differences E.g. in 1.0: <wsp:Policy wsu:Id="MyPolicy" > <wsoma:OptimizedMimeSerialization /> </wsp:Policy> In 1.1 WD: <wsp:Policy wsu:Id="MyPolicy" > <wsoma:MTOM /> </wsp:Policy> The current axis2-mtompolicy-1.4.jar implementation is used only by Rampart and is not implemented as a module. I think that the following can be done: 1) Make the mtom policy implementation as module that can be used at service and client side, so the MTOM policy can be processed correctly. This may rise some questions like where in the phases chain it should be set. I suppose some issues may rise here. For example with Rampart? 2) Extend the current implementation, so the "Optional" case is also processed (e.g. /wsoma:OptimizedMimeSerialization/@wsp:Optional="true"). 3) Later, when apropriate, adopt MTOM Serialization Policy Assertion 1.1 My general question: Is this in general ok as a concept for Axis2? Are there any plans in this area? Any comments on this will be appreciated. I am personally planing to make some prototyping of the above mentioned points, so any advices are welcome. Regards, Dobri
