[jboss-jira] [JBoss JIRA] (AS7-2362) Distribute client jars for remote EJB/JMS/etc

[Radoslav Husar (Updated) (JIRA)]

     [ https://issues.jboss.org/browse/AS7-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Radoslav Husar updated AS7-2362:
--------------------------------

              Summary: Distribute client jars for remote EJB/JMS/etc  (was: No client jars)
        Fix Version/s: 7.1.0.Final
    Affects Version/s: 7.1.0.CR1
                       7.0.2.Final
          Component/s: Build System


Updated Jira title and params. Discussion on dev list: 

Access to public API jars from (remote) client applications

http://lists.jboss.org/pipermail/jboss-as7-dev/2011-November/004567.html
http://lists.jboss.org/pipermail/jboss-as7-dev/2011-November/004771.html
http://lists.jboss.org/pipermail/jboss-as7-dev/2011-November/004772.html
http://lists.jboss.org/pipermail/jboss-as7-dev/2011-November/004773.html
                
> Distribute client jars for remote EJB/JMS/etc
> ---------------------------------------------
>
>                 Key: AS7-2362
>                 URL: https://issues.jboss.org/browse/AS7-2362
>             Project: Application Server 7
>          Issue Type: Feature Request
>          Components: Build System, Server
>    Affects Versions: 7.0.2.Final, 7.1.0.CR1
>            Reporter: Jim Tyrrell
>            Assignee: Jason Greene
>              Labels: eap6-ux
>             Fix For: 7.1.0.Final
>
>
> Typically customers use a client jar to get at a JBoss instance for JMS and other needs. These do not appear to be shipping today in the current build.  Some have suggested smaller client jars that encompass just a JMS use case, and EJB use case, etc.  Others have said the super jar is the way to go.

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