Nandana, Thanks for your suggestion, it has resolved the issue.
BTW, my axis2.xml was taken directly from the example java-first-jaxws (Axis2 1.4 distro), which has the security declared in all but the OutFaultFlow phase - not sure whether this is intended or a bug... Thanks, Alex -----Original Message----- From: Nandana Mihindukulasooriya [mailto:[EMAIL PROTECTED] Sent: May 3, 2008 1:10 AM To: axis-user@ws.apache.org Subject: Re: Axis2 1.4 and Rampart 1.3? Hi Alex, Are you using a custom axis2.xml in your scenario ? If so, can you please check that security phase is defined in <phaseOrder type="OutFaultFlow"> . You can find the discussion about this in axis2-dev list. You have to define the security phase as the last phase in OutFaultFlow phase order. Looking at the default axis2.xml [1] will help you to do that. thanks, nandana [1] - http://svn.apache.org/viewvc/webservices/axis2/trunk/java/modules/kernel/conf/axis2.xml?view=markup On 5/3/08, Savitsky, Alex <[EMAIL PROTECTED]> wrote: > Now it doesn't deploy at all, with exception: > > ERROR [org.apache.axis2.deployment.ServiceDeployer] - The > RecordWebService service, which is not valid, caused Did not find the > desired phase 'Security' while deploying handler > 'PolicyBasedSecurityOutHandler'. > org.apache.axis2.phaseresolver.PhaseException: Did not find the > desired phase 'Security' while deploying handler > 'PolicyBasedSecurityOutHandler'. > at > org.apache.axis2.phaseresolver.PhaseHolder.addHandler(PhaseHolder.java:75) > at > org.apache.axis2.phaseresolver.PhaseResolver.engageModuleToFlow(PhaseResolver.java:68) > at > org.apache.axis2.phaseresolver.PhaseResolver.engageModuleToOperation(PhaseResolver.java:104) > at > org.apache.axis2.phaseresolver.PhaseResolver.engageModuleToOperation(PhaseResolver.java:110) > at > org.apache.axis2.description.AxisOperation.onEngage(AxisOperation.java:158) > at > org.apache.axis2.description.AxisDescription.engageModule(AxisDescription.java:490) > at > org.apache.axis2.description.AxisService.onEngage(AxisService.java:785) > at > org.apache.axis2.description.AxisDescription.engageModule(AxisDescription.java:490) > at > org.apache.axis2.description.AxisDescription.engageModule(AxisDescription.java:453) > at > org.apache.axis2.deployment.DeploymentEngine.fillServiceGroup(DeploymentEngine.java:552) > at > org.apache.axis2.deployment.DeploymentEngine.addServiceGroup(DeploymentEngine.java:499) > at > org.apache.axis2.deployment.ServiceDeployer.deploy(ServiceDeployer.java:86) > at > org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136) > at > org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:597) > at > org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144) > at > org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:330) > at > org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:227) > at > org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:131) > at > org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServices(WarBasedAxisConfigurator.java:284) > at > org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:82) > at > org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:511) > at > org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:431) > > Did the configuration steps change? In 1.3, all I had to do was to > provide the policy element in services.xml, and this element seem to > have the same format in 1.4 samples as in 1.3 > > Regards, > > Alex > > -----Original Message----- > From: Nandana Mihindukulasooriya [mailto:[EMAIL PROTECTED] > Sent: May 2, 2008 2:37 PM > To: axis-user@ws.apache.org > Subject: Re: Axis2 1.4 and Rampart 1.3? > > Hi Alex, > Can you try with Rampart 1.4 RC [1] ? > > thanks, > nandana > > [1] - http://people.apache.org/~nandana/rampart-1.4/RC1/ > > On 5/3/08, Savitsky, Alex <[EMAIL PROTECTED]> wrote: > > Hi all, > > > > Does Axis2 1.4 work with Rampart 1.3? I have an existing app that > > works for the Axis2 1.3 and Rampart 1.3 combination, but when I > > upgrade server and client to 1.4, I get an exception from server: > > > > ERROR [org.apache.axis2.engine.AxisEngine] - Must Understand check > > failed for header > > http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-s > > ec > > ext-1.0.xsd > > : Security > > org.apache.axis2.AxisFault: Must Understand check failed for header > > http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-s > > ec > > ext-1.0.xsd > > : Security > > at > > org.apache.axis2.engine.AxisEngine.checkMustUnderstand(AxisEngine.ja > > va > > :102) at > > org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:166) > > at > > org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRe > > qu > > est(HTTPTransportUtils.java:275) at > > org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java: > > 13 > > 1) at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) > > ... > > > > Previously, Axis2 1.3 could understand this header without any > > problems. Is this a version incompatibility, or am I missing > > something > here? > > > > My service.xml looks like this: > > > > <service name="RecordWebService"> > > <messageReceivers> > > <messageReceiver > > mep="http://www.w3.org/2004/08/wsdl/in-only"; > > > > class="org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver" /> > > <messageReceiver > mep="http://www.w3.org/2004/08/wsdl/in-out"; > > > > class="org.apache.axis2.rpc.receivers.RPCMessageReceiver" /> > > </messageReceivers> > > <parameter name="ServiceClass" locked="false"> > > com.td.cems.ws.service.RecordWebServiceImpl > > </parameter> > > <module ref="addressing" /> > > <module ref="rampart" /> > > <wsp:Policy > xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy"; > > > > xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy"; > > xmlns:ramp="http://ws.apache.org/rampart/policy";> > > <wsp:ExactlyOne> > > <wsp:All> > > <wsp:Policy> > > <sp:SupportingToken> > > <wsp:Policy> > > > > <sp:UserNameToken> > > > > <wsp:Policy> > > > > <sp:HashPassword /> > > > > </wsp:Policy> > > > </sp:UserNameToken> > > </wsp:Policy> > > </sp:SupportingToken> > > </wsp:Policy> > > <ramp:RampartConfig> > > <ramp:passwordCallbackClass> > > > > com.td.cems.ws.service.PWCBHandler > > </ramp:passwordCallbackClass> > > </ramp:RampartConfig> > > </wsp:All> > > </wsp:ExactlyOne> > > </wsp:Policy> > > </service> > > > > Thanks, > > > > Alex > > > > > > ******************** > > NOTICE OF CONFIDENTIALITY > > This communication including any information transmitted with it is > > intended only for the use of the addressees and is confidential. > > If you are not an intended recipient or responsible for delivering > > the message to an intended recipient, any review, disclosure, > > conversion to hard copy, dissemination, reproduction or other use of > > any part of this communication is strictly prohibited, as is the > > taking or omitting of any action in reliance upon this communication. > > If you receive this communication in error or without authorization > > please notify us immediately by return e-mail or otherwise and > > permanently delete the entire communication from any computer, disk > > drive, or other storage medium. > > > > If the above disclaimer is not properly readable, it can be found at > > www.td.com/legal > > > > AVERTISSEMENT DE CONFIDENTIALITE > > Ce courriel, ainsi que tout renseignement ci-inclus, destiné > > uniquement aux destinataires susmentionnés, est confidentiel. Si > > vous n'êtes pas le destinataire prévu ou un agent responsable de la > > livraison de ce courriel, tout examen, divulgation, copie, > > impression, reproduction, distribution, ou autre utilisation d'une > > partie de ce courriel est strictement interdit de même que toute > > intervention ou abstraction à cet égard. Si vous avez reçu ce > > message par erreur ou sans autorisation, veuillez en aviser > > immédiatement l'expéditeur par retour de courriel ou par un autre > > moyen et supprimer immédiatement cette communication entière de tout > > système électronique. > > > > Si l'avis de non-responsabilité ci-dessus n'est pas lisible, vous > > pouvez le consulter à www.td.com/francais/legale > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
