[ https://jira.jboss.org/jira/browse/EJBTHREE-1536?page=com.atlassian.jira.... ] Andrew Lee Rubinger reopened EJBTHREE-1536: ------------------------------------------- -- 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/EJBTHREE-1536?page=com.atlassian.jira.... ] Andrew Lee Rubinger reassigned EJBTHREE-1536: --------------------------------------------- Assignee: Alessio Soldano (was: Andrew Lee Rubinger) Alessio, would you please confirm r79904 properly handles these API changes? If so assign back and I'll remove my comments from the code. -- 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/EJBTHREE-1536?page=com.atlassian.jira.... ] Alessio Soldano commented on EJBTHREE-1536: ------------------------------------------- The problem here is that the EndpointReference related methods were added to the WebServiceContext starting from the JAX-WS 2.1 specs. JBossWS-Native currently has a partial preview implementation of jaxws 2.1 (by Heiko/Thomas) that lives in jbossws-native-ext artifact (see WebServiceContext21 class). JBossWS-Metro, instead, is jaxws 2.1 compliant. The WebServiceContext was removed from the jbossws spi in the past (I think) because it actually does not belong to it. I think you could try importing the jaxws-api.jar artifact (groupid: javax.xml.ws, artifactid: jaxws-api, version 2.1) as we do in the jbossws-spi with provided scope. -- 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/EJBTHREE-1536?page=com.atlassian.jira.... ] Andrew Lee Rubinger commented on EJBTHREE-1536: ----------------------------------------------- I don't want to draw a dependency from EJB3 to the JAXWS API because we bring this in via jboss-metadata. So the EJB3 Implementation must conform to the API provided. My question is if r79904 is appropriate given this case. -- 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/EJBTHREE-1536?page=com.atlassian.jira.... ] Carlo de Wolf updated EJBTHREE-1536: ------------------------------------ Assignee: Carlo de Wolf (was: Alessio Soldano) Priority: Blocker (was: Major) It doesn't compile any more with OpenJDK6. -- 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