[ https://jira.jboss.org/jira/browse/JBWS-2257?page=com.atlassian.jira.plug... ] Alessio Soldano updated JBWS-2257: ---------------------------------- Fix Version/s: jbossws-metro-3.0.5 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBWS-2257?page=com.atlassian.jira.plug... ] Alessio Soldano updated JBWS-2257: ---------------------------------- Summary: Wrong WebServiceContext injected in EJB3 endpoints (was: Test WS-Addressing methods of WebServiceContext (JAX-WS 2.1)) Description: The current EJB3-WS integration causes a wrong WebServiceContext being injected in EJB3 endpoints when using JBossWS-Metro as the Sun's ws context should be used and not out WebServiceContextEJB3. This is an issue for instance for using the JAX-WS 2.1 specific methods of WebServiceContext, which are not implemented in native. public EndpointReference getEndpointReference(Element... referenceParameters); public <T extends EndpointReference> T getEndpointReference(Class<T> clazz, Element... referenceParameters); was: The WebServiceContext interface has the following methods in jaxws-2.1: public EndpointReference getEndpointReference(Element... referenceParameters); public <T extends EndpointReference> T getEndpointReference(Class<T> clazz, Element... referenceParameters); We need to check / provide a test using Metro ws-addressing implementation and verify it works with the WebServiceContext injected in EJB3 endpoints. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBWS-2257?page=com.atlassian.jira.plug... ] Alessio Soldano commented on JBWS-2257: --------------------------------------- This will be fixed for AS 5 only as the EJB3 implementation in AS 4.2.x creates its own WebServiceContext and is based on the JAX-WS 2.0 specs (which don't have the getEndpointReference wsa methods). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira