You have problem with security configuration. Looks like ws-sec inhandlers isin't executed.
On 6/16/07, Gabriel Baños <[EMAIL PROTECTED]> wrote:
Hi, I am developing a WS that requires both incoming and outgoing xml encryption and signing. I am following the examples in xfire distribution (the BookService one) and have managed to publish my own WS and write a Java client to invoke it. I am using JSR 181 Annotations to configure my InHandlers and OutHandlers. I am also using Spring support to configure XFire and get dependency injection. I am also following the example published in: http://arsenalist.com/2007/01/18/implementing-ws-security-with-jsr181-annotations-using-wss4j-in-xfire/ When a I call the WS an exception is thrown in the server with this stack trace: [INFO] DefaultFaultHandler - Fault occurred! <org.codehaus.xfire.fault.XFireFault: Invalid operation: { http://www.w3.org/2001/04/xmlenc#}EncryptedData>org.codehaus.xfire.fault.XFireFault: Invalid operation: {http://www.w3.org/2001/04/xmlenc#}EncryptedData at org.codehaus.xfire.service.binding.WrappedBinding.readMessage(WrappedBinding.java:42) at org.codehaus.xfire.soap.handler.SoapBodyHandler.invoke(SoapBodyHandler.java:42) at org.codehaus.xfire.handler.HandlerPipeline.invoke (HandlerPipeline.java:131) at org.codehaus.xfire.transport.DefaultEndpoint.onReceive(DefaultEndpoint.java:64) at org.codehaus.xfire.transport.AbstractChannel.receive(AbstractChannel.java:38) at org.codehaus.xfire.transport.http.XFireServletController.invoke(XFireServletController.java:304) at org.codehaus.xfire.transport.http.XFireServletController.doService(XFireServletController.java:129) at org.codehaus.xfire.transport.http.XFireServlet.doPost(XFireServlet.java:116) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at javax.servlet.http.HttpServlet.service(HttpServlet.java :820) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:367) at org.mortbay.jetty.security.SecurityHandler.handle (SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712) at org.mortbay.jetty.webapp.WebAppContext.handle (WebAppContext.java:405) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:211) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139) at org.mortbay.jetty.Server.handle(Server.java:286) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java :503) at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:841) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:639) at org.mortbay.jetty.HttpParser.parseAvailable (HttpParser.java:204) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:379) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:361) at org.mortbay.thread.BoundedThreadPool$PoolThread.run (BoundedThreadPool.java:442) Any clue ? I've been debugging xfire code but can't find the cause for this problem. As far as I could see, the exception is raised even before my security handlers get called. It seems that xfire handlers are not expecting encrypted data or something like that. Any help would be appreciated ! Thanks! -- Gabriel V. Baños --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
-- ----- When one of our products stops working, we'll blame another vendor within 24 hours. --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
