[jboss-jira] [JBoss JIRA] Commented: (JBAS-8164) Move jboss-ha-server-* jars from common/lib to server/all/lib

[Scott Marlow (JIRA)]

    [ https://jira.jboss.org/browse/JBAS-8164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12539626#action_12539626 ] 

Scott Marlow commented on JBAS-8164:
------------------------------------

The workaround for #1 (mod_cluster is noted above).  

The workaround for #2 deployers/clustering-deployer-jboss-beans.xml, is to comment out the contents of clustering-deployer-jboss-beans.xml which might cause ugly deployment error messages.  Email from Brian on the subjectl:
"
My guess is those deployers result in better error messages when people 
try to deploy clustered EJBs in default. Instead of getting CNFEs, those 
deployers introduce a dependency on HAPartition. That dependency can't 
be resolved, so the user gets a nice missing dependency error message 
instead of an obscure CNFE.
"  Or something to that effect.  I believe that commenting out the current beans and adding mock replacements if needed to handle giving proper deployment error messages would work.

3.  Didn't look into the ejb3 deployer error.  That work needs to happen if we decide to apply the patch attached to this jira.  I'll leave this assigned tome but not for an AS release. 

> Move jboss-ha-server-* jars from common/lib to server/all/lib
> -------------------------------------------------------------
>
>                 Key: JBAS-8164
>                 URL: https://jira.jboss.org/browse/JBAS-8164
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>    Affects Versions: 6.0.0.M3
>            Reporter: Paul Ferraro
>            Assignee: Scott Marlow
>             Fix For: 6.0.0.Final
>
>         Attachments: JBAS-8164.patch
>
>
> Currently, the build puts the following jars into common/lib:
> jboss-ha-server-api.jar
> jboss-ha-server-cache-jbc.jar
> jboss-ha-server-cache-spi.jar
> jboss-ha-server-core.jar
> This will likely cause classloader issues, especially for classes that extend/implement jbosscache or jgroups classes (e.g. CacheManager, ChannelFactory), since these jars reside in server/all/lib

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