[jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-925) Remove requirement to deploy JBM scoped in JB AS <= 4.2

[Tim Fox (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-925?page=all ]

Tim Fox updated JBMESSAGING-925:
--------------------------------

    Description: 
Currently JBM needs to be deployed as a scoped deployment in all the GA releases of JBoss AS.

This causes considerable configuration headaches for users and more than likely acts as a major barrier to adoption of JBM.

We currently scope because we use more recent versions of JBoss Remoting and JBoss AOP than the versions deployed in JBAS.

It appears that, other than JBM,  only EJB3 and parts of JBoss WS actually use AOP and remoting so instead of deploying scoped we should first verify whether WS and EJB3 work with the later versions of AOP and remoting, and if not we should patch AOP and remoting to get them to work.

Then we can overwrite the versions of remoting and aop in server/lib in the AS during the JBM install procedure and deploy unscoped - this would be a huge win for the project.

  was:
Currently JBM needs to be deployed as a scoped deployment in every all the GA releases of JBoss AS.

This causes considerable configuration headaches for users and more than likely acts as a major barrier to adoption of JBM.

We currently scope because we use more recent versions of JBoss Remoting and JBoss AOP than the versions deployed in JBAS.

It appears that, other than JBM,  only EJB3 and parts of JBoss WS actually use AOP and remoting so instead of deploying scoped we should first verify whether WS and EJB3 work with the later versions of AOP and remoting, and if not we should patch AOP and remoting to get them to work.

Then we can overwrite the versions of remoting and aop in server/lib in the AS during the JBM install procedure and deploy unscoped - this would be a huge win for the project.


> Remove requirement to deploy JBM scoped in JB AS <= 4.2
> -------------------------------------------------------
>
>                 Key: JBMESSAGING-925
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-925
>             Project: JBoss Messaging
>          Issue Type: Task
>    Affects Versions: 1.2.0.GA
>            Reporter: Tim Fox
>            Priority: Critical
>             Fix For: 1.2.0.SP1
>
>
> Currently JBM needs to be deployed as a scoped deployment in all the GA releases of JBoss AS.
> This causes considerable configuration headaches for users and more than likely acts as a major barrier to adoption of JBM.
> We currently scope because we use more recent versions of JBoss Remoting and JBoss AOP than the versions deployed in JBAS.
> It appears that, other than JBM,  only EJB3 and parts of JBoss WS actually use AOP and remoting so instead of deploying scoped we should first verify whether WS and EJB3 work with the later versions of AOP and remoting, and if not we should patch AOP and remoting to get them to work.
> Then we can overwrite the versions of remoting and aop in server/lib in the AS during the JBM install procedure and deploy unscoped - this would be a huge win for the project.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira