[jboss-jira] [JBoss JIRA] Commented: (JBAS-5284) Cannot use a scoped loader repository in deploy-hasingleton deployments

[Galder Zamarreno (JIRA)]

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

Galder Zamarreno commented on JBAS-5284:
----------------------------------------

Hmmm, I've managed to deploy HASingleton barrier EJB3 beans without any issues. 
What issues are you refering to with "Note that this will not work properly for EJB 
deployments."?

Also, as a side note, I see that jboss-app has <depends/> missing. Scott says the 
following in: http://www.jboss.com/?module=bb&op=viewtopic&t=96686&start=10

"jboss-app.xml does not support depends because its not a component deployment. 
Its more of a packing notion. Anything needing a dependency in an ear would have its 
own depends support in its descriptor. "

Wouldn't it make sense to have a <depends/> for an EAR indicating that the EAR can 
be deployed as a singleton without putting it in deploy-hasingleton? That probably 
be a preferred way to deploy an EAR as singleton.

> Cannot use a scoped loader repository in deploy-hasingleton deployments
> -----------------------------------------------------------------------
>
>                 Key: JBAS-5284
>                 URL: https://jira.jboss.org/jira/browse/JBAS-5284
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-4.2.2.GA
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>
> If you try to add a loader-repository element to a deploy-hasingleton deployment, you get something like this:
> Only the root deployment can set the loader repository, ignoring config=LoaderRepositoryConfig(repositoryName: jboss.dataintegration:sar=dataintegration.sar, repositoryClassName: org.jboss.mx.loading.HeirarchicalLoaderRepository3, configParserClassName: org.jboss.mx.loading.HeirarchicalLoaderRepository3ConfigParser, repositoryConfig: java2ParentDelegation=false)
> I suspect this is because the deploy-hasingleton dir itself is being treated as the root deployment.

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