Hi Julio, I checked your process. I think the issue is the name of the property used to set the policy. It has been renamed from 'security.policy' to 'security,policy.file' I'm sorry for the inconvenience. I'll update the doc right away.
Alexis On Thu, Apr 23, 2009 at 2:59 PM, Julio Cesar Damasceno <[email protected]>wrote: > Hi, > > I'm using ode 1.3 from trunk rev: 768068 > > I'm trying to invoke a secure webservice in my BPEL composition, the web > service was using rampart and I build a client and works fine, but the ODE > doesn't sent the request for web service using the rampart configuration > file, i got the following message: > > I attach my BPEL process. > > --- > Julio > > Service response: > <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv=" > http://schemas.xmlsoap.org/soap/envelope/";><soapenv:Header<http://schemas.xmlsoap.org/soap/envelope/%22%3E%3Csoapenv:Header>xmlns:wsa=" > http://www.w3.org/2005/08/addressing";><wsa:Action>http://www.w3.org/2005/08/addressing/soap/fault</wsa:Action><wsa:RelatesTo>uuid:hqejbhcnphr47xeja3hb15</wsa:RelatesTo></soapenv:Header><soapenv:Body><soapenv:Fault<http://www.w3.org/2005/08/addressing%22%3E%3Cwsa:Action%3Ehttp://www.w3.org/2005/08/addressing/soap/fault%3C/wsa:Action%3E%3Cwsa:RelatesTo%3Euuid:hqejbhcnphr47xeja3hb15%3C/wsa:RelatesTo%3E%3C/soapenv:Header%3E%3Csoapenv:Body%3E%3Csoapenv:Fault>xmlns:wsse=" > http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";><faultcode>wsse:InvalidSecurity</faultcode><faultstring>Missing<http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd%22%3E%3Cfaultcode%3Ewsse:InvalidSecurity%3C/faultcode%3E%3Cfaultstring%3EMissing>wsse:Security > header in request</faultstring><detail > /></soapenv:Fault></soapenv:Body></soapenv:Envelope> > DEBUG - GeronimoLog.debug(66) | Received response for MEX > {PartnerRoleMex#hqejbhcnphr47xeja3hb12 [PID null] calling > [email protected](...)} > ERROR - GeronimoLog.error(108) | Unable to process response: null > java.lang.NullPointerException > at > org.apache.ode.axis2.soapbinding.SoapMessageConverter.inferFault(SoapMessageConverter.java:557) > at > org.apache.ode.axis2.soapbinding.SoapMessageConverter.parseSoapFault(SoapMessageConverter.java:533) > at > org.apache.ode.axis2.soapbinding.SoapExternalService.reply(SoapExternalService.java:340) > at > org.apache.ode.axis2.soapbinding.SoapExternalService.invoke(SoapExternalService.java:191) > at > org.apache.ode.axis2.MessageExchangeContextImpl.invokePartnerUnreliable(MessageExchangeContextImpl.java:68) > at > org.apache.ode.bpel.engine.PartnerLinkPartnerRoleImpl$UnreliableInvoker.run(PartnerLinkPartnerRoleImpl.java:345) > at > org.apache.ode.bpel.engine.ODEProcess$ProcessRunnable.run(ODEProcess.java:1215) > at > org.apache.ode.bpel.engine.BpelServerImpl$ServerRunnable.run(BpelServerImpl.java:927) > at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) > at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) > at java.util.concurrent.FutureTask.run(Unknown Source) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) > at java.lang.Thread.run(Unknown Source) > > > I'm follow the ODE user guide with endpoint configuration and supplying a > xml policy file. > > http://ode.apache.org/user-guide.html#UserGuide-WSSecuritywithAxis2integrationlayer > > >
