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

Tue Jul 22 10:52:16 EDT 2008

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

Adrian Brock commented on JBAS-5284:
------------------------------------

"I don't believe undeploying a URLDeploymentScanner causes an undeployment of previously deployed content."

You mean stopping.

We'll that's a bug then :-)
https://jira.jboss.org/jira/browse/JBAS-5790

> 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