[jboss-jira] [JBoss JIRA] Closed: (JBAS-5284) Cannot use a scoped loader repository in deploy-hasingleton deployments
[
https://jira.jboss.org/jira/browse/JBAS-5284?page=com.atlassian.jira.plug...
]
Adrian Brock closed JBAS-5284.
------------------------------
Resolution: Rejected
You can't use a loader repository in deploy-hasingleton
because it is deploying the whole directory as a single deployment.
If you want individual deployments then should make
deploy-hasingleton-service.xml deploy a URLDeploymentScanner
such that it deploys individual applications in deploy-hasingleton.
e.g. Change the start/stop in deploy-hasingleton-service.xml to
deploy the deployment scanner (see below - hasingleton-scanner-service.xml)
<attribute name="TargetStartMethod">deploy</attribute>
<attribute
name="TargetStartMethodArgument">${jboss.server.home.url}/hasingleton-scanner-service.xml</attribute>
<attribute name="TargetStopMethod">undeploy</attribute>
<attribute
name="TargetStopMethodArgument">${jboss.server.home.url}/hasingleton-scanner-service.xml</attribute>
Then create a server/all/hasingleton-scanner-service.xml
with something contents like (i.e. scan and deploy the contents of deploy-hasingleton).
<server>
<mbean code="org.jboss.deployment.scanner.URLDeploymentScanner"
name="jboss.deployment:type=DeploymentScanner,flavor=URL,name=HASingleton">
<depends
optional-attribute-name="Deployer">jboss.system:service=MainDeployer</depends>
<attribute
name="URLComparator">org.jboss.deployment.DeploymentSorter</attribute>
<attribute name="FilterInstance"
attributeClass="org.jboss.deployment.scanner.DeploymentFilter"
serialDataType="javaBean">
<!-- Files starting with theses strings are ignored -->
<property name="prefixes">#,%,\,,.,_$</property>
<!-- Files ending with theses strings are ignored -->
<property name="suffixes">#,$,%,~,
\,v,.BAK,.bak,.old,.orig,.tmp,.rej,.sh</property>
<!-- Files matching with theses strings are ignored -->
<property
name="matches">.make.state,.nse_depinfo,CVS,CVS.admin,RCS,RCSLOG,SCCS,TAGS,core,tags</property>
</attribute>
<!-- Frequency in milliseconds to rescan the URLs for changes -->
<attribute name="ScanPeriod">5000</attribute>
<!-- A flag to disable the scans -->
<attribute name="ScanEnabled">true</attribute>
<!-- HERE !!!!!!!!!! Hot deploy hasingleton as individual
applications -->
<attribute name="URLs">
deploy-hasingleton/
</attribute>
<attribute name="RecursiveSearch">True</attribute>
</mbean>
</server>
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