[jboss-jira] [JBoss JIRA] (AS7-2060) Add correct package version information to packages exported by the javaee.api module

[Aaron Whiteside (Issue Comment Edited) (JIRA)]

    [ https://issues.jboss.org/browse/AS7-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633840#comment-12633840 ] 

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.
                  
> Add correct package version information to packages exported by the javaee.api module
> -------------------------------------------------------------------------------------
>
>                 Key: AS7-2060
>                 URL: https://issues.jboss.org/browse/AS7-2060
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: EE, OSGi
>    Affects Versions: 7.0.2.Final
>            Reporter: Aaron Whiteside
>            Assignee: Thomas Diesler
>
> Currently all packages exported by the module javaee.api to OSGi land are exported with version 0.0.0.
> A lot of existing bundles that use classes/packages from javax.* specify a version, which makes this not work correctly in JBoss 7 AS.
> This makes bundles that depend on for example: javax.jms;version=1.1 not work.
> The correct version information should be exported by the javaee.api bundle. Because at the moment it's pretty much useless with the existing libraries/bundles.

--
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