Hi Willem, > Can you tell me if you are trying to call the service which is deploied > into the web container ? > And if you can show us you test case to reproduce it , we will solve the > issue soon.
actually, the problem with the JaxWsProxyFactoryBean not being serializable happens on the client side, not within the service. I've deployed the CXFServlet in a web container (resin 3.1.1 - which doesn't yet support @Resource WebServiceContext, but that's not your problem ;-)). My problem is, that when I generate a proxy per user-session on the client side, the proxy doesn't get serialized into the session-space and on getting back to it, I get a NPE. It might be really the only fault-tolerant way to submit the session-id with every request... Best regards, --- Jan.
