[ https://issues.jboss.org/browse/AS7-2060?page=com.atlassian.jira.plugin.s... ] Thomas Diesler resolved AS7-2060. --------------------------------- Resolution: Rejected This has been fixed as part of AS7-1974 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-2060?page=com.atlassian.jira.plugin.s... ] Aaron Whiteside commented on AS7-2060: -------------------------------------- I've taken a look at the pull request for AS7-1601 and can only see a reference to a few javax.* packages in the javaee.api module. {code} Bundle-SymbolicName: javaee.api Export-Package: javax.inject,javax.servlet;version=3.0,javax.servlet.annotation;version=3.0,javax.servlet.descriptor;version=3.0,javax.servlet.http;version=3.0,javax.transaction;version=1.1,javax.transaction.xa;version=1.1 {code} I don't see how this change or any other change in the pull request will be setting the version for javax.jms or javax.transaction, javax.validation, javax.ws, javax.inject, etc, etc the list goes on. All these packages will still be exported with version 0.0.0. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-2060?page=com.atlassian.jira.plugin.s... ] Thomas Diesler edited comment on AS7-2060 at 10/11/11 10:14 AM: ---------------------------------------------------------------- The current OSGi integration supports the documented set of functionality that is also verified by automated tests. If you look closely, you see * javax.inject * javax.servlet * javax.transaction being covered by this change. Indeed javax.ws, javax.jms are not covered (yet). was (Author: thomas.diesler): The current OSGi integration supports the documented set of functionality that is also verified by automated tests. If you look closely, you see * javax.inject * javax.servlet * javax.transaction beeing covered by this change. Indeed javax.ws, javax.jms are not covered (yet). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-2060?page=com.atlassian.jira.plugin.s... ] Thomas Diesler edited comment on AS7-2060 at 10/11/11 10:15 AM: ---------------------------------------------------------------- The current OSGi integration supports the documented set of functionality that is also verified by automated tests. If you look closely, you see * javax.inject * javax.servlet * javax.transaction being covered by this change. Indeed javax.ws, javax.jms are not covered (yet). What is the specific use case for OSGi/JMS integration? was (Author: thomas.diesler): The current OSGi integration supports the documented set of functionality that is also verified by automated tests. If you look closely, you see * javax.inject * javax.servlet * javax.transaction being covered by this change. Indeed javax.ws, javax.jms are not covered (yet). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-2060?page=com.atlassian.jira.plugin.s... ] Aaron Whiteside edited comment on AS7-2060 at 10/11/11 10:26 AM: ----------------------------------------------------------------- The issue I opened is against all javax.* api's not the ones you specified: * javax.inject * javax.servlet * javax.transaction So I am not sure why the issue was rejected - as not all the javax.* api's have version information and this is not fixed in AS7-1601. The workaround I provided with javax.jms and javax.transaction was an example - the problem that not all javax.* packages have version information still remains. My specific use case was around using JMS in OSGi by grabbing a reference to the connection factory java:/JmsXA from JNDI and using that to send/receive messages. But again I stress that this issue I opened was not against my specific use case specifically, and is more general. Put another way if you are going to expose a boatload of javax.* packages from the javaee.api and javax.api modules. Then it might as well be done correctly - because the currently exported list of packages is not consumable by pretty much all libraries/bundles/projects out there. Since they all specific a correct version. Take for example the spring libraries/bundles: * spring-jms-3.0.6.RELEASE.jar * spring-tx-3.0.6.RELEASE.jar etc.. was (Author: Aaron.Whiteside): The issue I opened is against all javax.* api's not the ones you specified: * javax.inject * javax.servlet * javax.transaction So I am not sure why the issue was rejected - as not all the javax.* api's have version information and this is not fixed in AS7-1601. The workaround I provided with javax.jms and javax.transaction was an example - the problem that not all javax.* packages have version information still remains. My specific use case was around using JMS in OSGi by grabbing a reference to the connection factory java:/JmsXA from JNDI and using that to send/receive messages. But again I stress that this issue I opened was not against my specific use case specifically, and is more general. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-2060?page=com.atlassian.jira.plugin.s... ] Thomas Diesler commented on AS7-2060: ------------------------------------- ok, I see you point. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-2060?page=com.atlassian.jira.plugin.s... ] Thomas Diesler updated AS7-2060: -------------------------------- Fix Version/s: 7.1.0.Beta1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-2060?page=com.atlassian.jira.plugin.s... ] Thomas Diesler commented on AS7-2060: ------------------------------------- We now explicitly add these capabilities {code} <capability name="javax.servlet.api"/> <capability name="javax.transaction.api"/> {code} which have proper version metadata. The general javaee.api capability is gone. The javax.jms.api is not tested, therefore not added by default. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-2060?page=com.atlassian.jira.plugin.s... ] Aaron Whiteside commented on AS7-2060: -------------------------------------- Cool, That makes it much easier to add additional modules with the correct version metadata. Any idea when javax.jms.api might be tested, would you want me to open another issue for jms specifically? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira