On Feb 28, 2007, at 12:14 PM, Jarek Gawor wrote:
David, Here are two fairly simple things that we need to do get closer to the spec compliance with EJB and JAX-WS support: 1) OpenEJB must recognize and inject @Resource WebServiceContext resource. This is like the EJBContext object I think (not looked up in JNDI and there is no DD XML for it). So somehow we must be able to pass WebServiceContext implementation from within Geronimo to the EJB container. Maybe somehow through the EjbDeployment object.
Sure. What do we have in place for processing @Resource WebServiceContext for Servlets? Should be easy to figure out how to do it on the EJB side based on what's done in the Servlet side.
2) The InvocationContext.getContextData() must return the same exact Map object as WebServiceContext.getMessageContext() returns. I think this just pretty much depends on 1).
Good info. I'm not really following the new web service stuff, so if you run into more requirements like this definitely continue to post.
Of course there are other things like the handler/interceptor stuff that we need to work out. And I think some security issues that I need to read more about.
Cool. If you encounter any more handler/interceptor stuff like the above that we should be aware of definitely post. In fact now that I mention it I also seem to remember that for web services InvocationContext.getParameters() and getMethod() don't apply and shouldn't be used. I can't remember if the result is an exception or null, though.
-David
