Hi Dobri, I mean that the "optional" MTOM configuration is not implemented (i.e. > /wsoma: OptimizedMimeSerialization/@wsp:Optional="true"). >
Yep. Created a JIRA for that [1] and fixed it. > 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? > My concern was that whether people will like to add a new module just to do MTOM configuration. But when we think it though it seems it is reasonable to have a module for this. So what I thought was a module that sets the the MTOM parameters according to the policy. We can also do the other way around too by setting the policy when MTOM is enabled using the parameters. So when MTOM is configured either way, the policy will appear in the WSDL. I have created a prototype for the module [2]. People will still be able to set MTOM parameters without engaging this module if there don't care about policy and everything will be backward compatible. We can create a private custom assertion too which will contain configuration options described here [2]. This will be something similar to RampartConfig assertion in Rampart module. WDYT ? thanks, nandana [1] - http://issues.apache.org/jira/browse/AXIS2-4046 [2] - https://wso2.org/repos/wso2/people/nandana/mtompolicy/ [3] - http://wso2.org/library/264 > [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 >>> >>> <http://www.wso2.org> >> > > -- Nandana Mihindukulasooriya WSO2 inc. http://nandana83.blogspot.com/ http://www.wso2.org
