Hi Dimuthu, Thanks.
2007/10/16, Dimuthu Leelarathne <[EMAIL PROTECTED]>: > Hi, > > In the attachment you have asked two questions. > > 1) On the server side, why the StAXSOAPModelBuilder is used not is > MTOMStAXSOAPModelBuilder? > I don't the answer to this question. Maybe Axiom veterans can help you. > > 2) The property of OMText is not binary. Why? > This is a bug, please report a jira at > https://issues.apache.org/jira/browse/RAMPART > > We'll fix the second problem for the next release. > > Thank you, > Dimuthu > > > > On Tue, 2007-10-16 at 10:20 +0800, Wenshuang Sun wrote: > > Hi, > > I have problem about MTOM+Rampart, while I add binay node at client and send > > the binay node to server side, but at server side, > > I receive the node that is not binay node, is plain text node, why? I > > already regist the problem at > > http://www.nabble.com/About-MTOM+Rampart-t4506654.html and > > there is a picture about the problem, please give me some advice. Thanks. > > > > I use axis2 1.2+Rampart1.2 and axis2 1.3+Rampart1.3, there is still the > > problem. > > the detail info is as the following. > > At axis2 client side, I add one binary node in soap message by MTOM, the > > following is the source code. > > > > OMElement imageElement = fac.createOMElement("image", omNs); > > javax.activation.DataHandler dataHandler = new > > javax.activation.DataHandler(new FileDataSource("SomeFile")); > > //create an OMText node with the above DataHandler and set > > optimized to true > > OMText textData = *fac.createOMText(dataHandler, true);* > > imageElement.addChild(textData); > > At axis2 client side,I use the following ws-policy settings. > > <wsp:Policy wsu:Id="MTOMOverTransport" > > xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"; > > xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy"; > > xmlns:wsoma="http://schemas.xmlsoap.org/ws/2004/09/policy/optimizedmimeserialization";> > > <wsoma:OptimizedMimeSerialization wsp:Optional="true"/> > > <ramp:RampartConfig xmlns:ramp="http://ws.apache.org/rampart/policy";> > > <ramp:user>client</ramp:user> > > <ramp:encryptionUser>service</ramp:encryptionUser> > > > > <ramp:passwordCallbackClass>sample.PWCBHandler</ramp:passwordCallbackClass> > > > > <ramp:signatureCrypto> > > <ramp:crypto > > provider="org.apache.ws.security.components.crypto.Merlin"> > > <ramp:property > > name="org.apache.ws.security.crypto.merlin.keystore.type">JKS</ramp:property> > > <ramp:property > > name="org.apache.ws.security.crypto.merlin.file">client.jks</ramp:property> > > <ramp:property > > name="org.apache.ws.security.crypto.merlin.keystore.password">client</ramp:property> > > </ramp:crypto> > > </ramp:signatureCrypto> > > <ramp:encryptionCypto> > > <ramp:crypto > > provider="org.apache.ws.security.components.crypto.Merlin"> > > <ramp:property > > name="org.apache.ws.security.crypto.merlin.keystore.type">JKS</ramp:property> > > <ramp:property > > name="org.apache.ws.security.crypto.merlin.file">client.jks</ramp:property> > > <ramp:property > > name="org.apache.ws.security.crypto.merlin.keystore.password">client</ramp:property> > > </ramp:crypto> > > </ramp:encryptionCypto> > > </ramp:RampartConfig> > > </wsp:Policy> > > > > At server side, I use the following ws-policy settings. > > <wsp:Policy wsu:Id="MTOMOverTransport" > > > > xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"; > > > > xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy"; > > > > xmlns:wsoma="http://schemas.xmlsoap.org/ws/2004/09/policy/optimizedmimeserialization";> > > <wsoma:OptimizedMimeSerialization > > wsp:Optional="true"/> > > <ramp:RampartConfig > > > > xmlns:ramp="http://ws.apache.org/rampart/policy";> > > <ramp:user>service</ramp:user> > > > > <ramp:encryptionUser>client</ramp:encryptionUser> > > <ramp:passwordCallbackClass> > > sample.PWCBHandler > > </ramp:passwordCallbackClass> > > > > <ramp:signatureCrypto> > > <ramp:crypto > > > > provider="org.apache.ws.security.components.crypto.Merlin"> > > <ramp:property > > > > name="org.apache.ws.security.crypto.merlin.keystore.type"> > > JKS > > </ramp:property> > > <ramp:property > > > > name="org.apache.ws.security.crypto.merlin.file"> > > service.jks > > </ramp:property> > > <ramp:property > > > > name="org.apache.ws.security.crypto.merlin.keystore.password"> > > service > > </ramp:property> > > </ramp:crypto> > > </ramp:signatureCrypto> > > <ramp:encryptionCypto> > > <ramp:crypto > > > > provider="org.apache.ws.security.components.crypto.Merlin"> > > <ramp:property > > > > name="org.apache.ws.security.crypto.merlin.keystore.type"> > > JKS > > </ramp:property> > > <ramp:property > > > > name="org.apache.ws.security.crypto.merlin.file"> > > service.jks > > </ramp:property> > > <ramp:property > > > > name="org.apache.ws.security.crypto.merlin.keystore.password"> > > service > > </ramp:property> > > </ramp:crypto> > > </ramp:encryptionCypto> > > </ramp:RampartConfig> > > </wsp:Policy> > >
