Hi Nandana,
> It seems that this WS-MTOMPolicy implementation is very basic. Currently >> there is only one possible assertion that can be used and it just specifies >> if MTOM should be used: >> >> <wsoma:OptimizedMimeSerialization xmlns:wsoma=" >> http://schemas.xmlsoap.org/ws/2004/09/policy/optimizedmimeserialization >> "/> >> >> This is obvious looking at the >> org.apache.axis2.policy.builders.MTOMAssertionBuilder and >> org.apache.axis2.policy.model.MTOMAssertion implementations. The only >> possible way to specify that MTOM is optional is programmatically, but not >> using a policy. >> > It seems WS-MTOMAssertion spec only defines OptimizedMimeSerialization > assertion. So Axis2 mtom-policy module seems to cover the WS-MTOMPolicy > spec. But this policy is not considered in Axis2 and only enableMTOM > parameter is considered. > I mean that the "optional" MTOM configuration is not implemented (i.e. /wsoma: OptimizedMimeSerialization/@wsp:Optional="true"). If we read the point 2.3 from the specification: 3.2 Assertion Syntax The normative outline for the Optimized Mime Serialization policy assertion is: * <wsoma:OptimizedMimeSerialization ... /> The following describes additional constraints on the outline listed above: /wsoma:OptimizedMimeSerialization A policy assertion that specifies that MTOM [MTOM] MUST be used in messages sent to the Web service. It also specifies that responses from the Web service MUST be optimized using MTOM [MTOM], i.e. that the messages must be sent using the application/xop+xml mime type. * /wsoma:OptimizedMimeSerialization/@wsp:Optional="true" Per WS-Policy [WS-Policy], this is compact notation for two policy alternatives, one with and one without the assertion. This indicates that the behavior indicated by the assertion is optional, specifically that non-MTOM-encoded exchanges are also supported by the endpoint. * /wsoma:OptimizedMimeSerialization/@any This is an extensibility mechanism to allow additional attributes to be added to the element. > > What about covering the whole WS-MTOMPolicy specification and creating a >> separate module that can be engaged/disengaged when a MTOM policy is find >> into the WSDL. Doing so a client can make use of MTOM throughout reading the >> policy assertion and engaging the module. >> > > We can have a module which can check whether the > "wsoma:OptimizedMimeSerialization" assertion is present in the effective > policy of the service and set the parameters accordingly. We can even have > a private assertion through which we can provide configuration parameters > [1] related to MTOM and the module can set the parameters on Axis2 > accordingly. This way we can allow MTOM configuration to be done through > policy without effecting the backward compatibility. But I am not sure > introducing a module for this would be a overkill. > You are right. I can agree this may cause an overkill, but can you be more concrete? Anyway I think that the natural way to configure a QoS is making use of policies and modules? All these give us lots of benefits (e.g. interoperability, modularity etc.). Please, can you give the cons of doing that. IMHO I can agree this will consume lots of efforts for creating a module that give a little functionality at the end and module that we do not expect to develop too much in the future (compared to Rampart for example). Anyway we should decide if this is ok for the long term. Isn't that inevitable to move MTOM in a module at some point of time? > > thanks, > nandana > > Thanks, Dobri > > [1] - http://wso2.org/library/264 > > >> On Thu, Jul 17, 2008 at 8:31 PM, Thilina Gunarathne <[EMAIL PROTECTED]> >> wrote: >> >>> Axis2 has a mtom-policy implementation and I hope it works, but I have >>> not tested it personally... >>> >>> We went a little bit further with enableMTOM... >>> >>> http://thilinag.blogspot.com/2007/07/improved-apache-axis2-attachment.html >>> >>> thanks, >>> Thilina >>> >>> >>> On Thu, Jul 17, 2008 at 6:00 AM, Dobri Kitipov < >>> [EMAIL PROTECTED]> wrote: >>> >>>> Hi all, >>>> currently I am researching the possibilities to make MTOM configuration >>>> more advanced, than just saying that enableMTOM=true. For example it will >>>> be >>>> nice to specify a threshold that defines the size of the binary when MTOM >>>> to >>>> be activated etc. >>>> I want to ask and if there are any plans to support the WS-MTOMPolicy. >>>> Is there any willing/steps into the community to support this in the near >>>> future. >>>> >>>> >>>> Regards, Dobri >>>> >>> >>> >>> >>> -- >>> Thilina Gunarathne - http://thilinag.blogspot.com >> >> >> > > > -- > Nandana Mihindukulasooriya > WSO2 inc. > > http://nandana83.blogspot.com/ > http://www.wso2.org >
