Hi Ruchith, Thanks for the fast reaction. I've downloaded your new axiom-dom jar, however I still got the same exception... Then I removed the axiom-dom jar altogether (from both the client respository and the server), and I still got the very same exception (so no ClassNotFoundException...). Further investigation showed that the org.apache.axiom.om.impl.dom.CharacterImpl was used from the axiom-api-1.0.jar, NOT from the axiom-dom jar. I unpacked both jars and compared them, it seems to me that the axiom-dom jar is actually a subset of the classes in the axiom-api jar. And all of these (except for org.apache.axiom.om.impl.dom.CharacterImpl and org.apache.axiom.om.impl.dom.TextImpl) were identical. I cannot imagine that it's meant to be so...
I cannot remove the axiom-api-1.0.jar as the startup of Axis2 under Tomcat fails... I can try to mess around with the order in the classpath of both the client repository and the server, but I guess it would be easier (and better) to solve this duplication by either merging the two jars or removing the duplicate classes from the axiom-api jar. Thanks again, / Roy --- Ruchith Fernando <[EMAIL PROTECTED]> wrote: > Hi Roy, > > Thank you for reporting this problem ... I traced > the issue to the > org.apache.axiom.om.impl.dom.CharacterImpl of the > OM-DOM > implementation (DOOM) and this is fixed in SVN > revision : 406708 > > Please replace your axiom-dom-1.0.jar with this [1] > and try again. > > Thanks, > Ruchith > > [1] > http://people.apache.org/~ruchithf/axiom-dom-406708.jar > > On 5/15/06, Reshef Roy <[EMAIL PROTECTED]> wrote: > > Hi all, > > > > This is maybe a stupid problem resluting from the > fact > > that I am not a WS/SOAP expert, but I've been > fighting > > with it for almost a week now with no results, > > therefore any kind of help will be appreciated. > > > > I am using Axis2 1.0 and jre1.5.0_06. > > My service is deployed on Tomcat 5.5.16 (Axis2 1.0 > WAR > > distribtion) and my test client is a simple > standalone > > Java application, which uses an Axis2 repository > and > > which is invoked using an ANT build file. > > > > On both the client and the server I engage the > > addressing-1.0 module and the security > (rampart-1.0) > > module; WSS4J version is 1.5.0. Both the client > and > > the server are configured to enable MTOM. > > > > When I DO NOT configure any usage of the rampart > > module (in both axis2.xml of the client repo and > > services.xml of the AAR service), everything goes > well > > - the SOAP messages are going back and forth and > are > > succesfully consumed by the service and the > client, > > respectively. > > > > When I configure the client->server message > > (OutflowSecurity of the client and InflowSecurity > of > > the service) with the actions "Timestamp Signature > > Encrypt" (in a similar manner to the security > sample), > > everything goes well. > > However, when I configure the server->client > message > > (OutflowSecurity of the service and InflowSecurity > of > > the client) with the actions "Timestamp Signature > > Encrypt" (in a similar manner to the security > sample), > > I get the following exception on the server side. > As > > it complains on the SOAP envelope and states > > > <soapenv:Code><soapenv:Value>soapenv:Sender</soapenv:Value></soapenv:Code> > > it seems to me that the problem is in my incoming > > (client->server) message. I have tried to locate > it, > > but in vain. > > [rest of message truncated] __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
