Hi Thilina, thank you for the answer. I have some questions. 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. Searching the Axis I can see that this implementation is used only in Rampart (org.apache.rampart.policy.RampartPolicyBuilder). 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. Any thoughts? Thank you in advance! Regards, Dobri 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
