Hi, as far as MTOM is concerned, defining the XOP elements as seperate parts in a rpc/literal operation is allowed but certainly not required, they can be part of a single parts infoset.. (one of the key points of MTOM as far as I can see..) regarding the use of the element attribute instead of type, this seems to be in conflict with basic-profile, if you run the basic-profile validations against the wsdl you will get the same error.. on the other hand, this is a bit strange because the BP states that message parts not explicitely referenced by the corresponding binding in a rpc/literal operation can by defined using the element attribute.. (R2207)
this doesn't help you out much I guess.. lets see what light Thomas/Jason can shed on this issue.. :-) regards! /Ole eviware.com View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3948606#3948606 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3948606 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
