This content has been marked as final.
Show 7 replies
-
1. Re: AbstractVFSParsingDeployer doesn't kick in upon server r
jaikiran Mar 4, 2009 6:50 AM (in response to heiko.braun)2009-03-04 11:50:51,903 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] (main) Fully Deployed vfsfile:/Users/hbraun/dev/prj/jboss/tags/JBoss_5_0_0_GA/build/output/jboss-5.0.0.GA/server/default/deploy/Simple-Alpha2.par
This message is just a note that the deployment was passed through the list of the deployers available. It doesn't actually mean that any of the deployers in the list of deployers was found relevant for the deployment.
I usually enable TRACE level logging to get more information. Something like these:2009-03-04 17:11:55,399 TRACE [org.jboss.deployers.plugins.deployers.DeployersImpl] Deployer org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer@1406eb6 not relevant for vfsfile:/home/jpai/business/jboss/wc/jbossas/projects/ejb3/trunk/nointerface/src/test/resources/deployers/
which shows me whether the deployer was considered relevant for the deployment -
2. Re: AbstractVFSParsingDeployer doesn't kick in upon server r
heiko.braun Mar 4, 2009 6:59 AM (in response to heiko.braun)I did dig a little further and ame to this point:
public abstract class AbstractVFSParsingDeployer<T> extends AbstractParsingDeployerWithOutput<T> implements FileMatcher { ... // try all name+suffix matches List<VirtualFile> files = vfsDeploymentUnit.getMetaDataFiles(name, suffix); switch (files.size()) { case 0 : return null; case 1 : return parseAndInit(vfsDeploymentUnit, files.get(0), root); default : return handleMultipleFiles(vfsDeploymentUnit, root, files); } ...
Seems that the lookup by name+suffix returns an empty list.
What I don't understand is why this behaves differently when I copy an archive to the deploy directory when the server is running. -
3. Re: AbstractVFSParsingDeployer doesn't kick in upon server r
emuckenhuber Mar 4, 2009 7:39 AM (in response to heiko.braun)"heiko.braun@jboss.com" wrote:
What I don't understand is why this behaves differently when I copy an archive to the deploy directory when the server is running.
This is a known issue that the jarExtensions are not picked up when starting AS. This will be fixed in 5.1.
You would need to add your jarExtension to the bootstrap/deployers.xml for the moment like it's done here:<bean name="JARStructure" class="org.jboss.deployers.vfs.plugins.structure.jar.JARStructure"> ... <value>.spring</value> <value>.rails</value> <value>.esb</value> </bean>
-
4. Re: AbstractVFSParsingDeployer doesn't kick in upon server r
heiko.braun Mar 4, 2009 3:11 PM (in response to heiko.braun)Thanks. Do you know the JIRA number so I can monitor it?
-
5. Re: AbstractVFSParsingDeployer doesn't kick in upon server r
heiko.braun Mar 4, 2009 3:13 PM (in response to heiko.braun)OK, got it: https://jira.jboss.org/jira/browse/JBAS-6274
-
6. Re: AbstractVFSParsingDeployer doesn't kick in upon server r
adrian.brock Mar 5, 2009 5:54 AM (in response to heiko.braun)"jaikiran" wrote:
2009-03-04 17:11:55,399 TRACE [org.jboss.deployers.plugins.deployers.DeployersImpl] Deployer org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer@1406eb6 not relevant for vfsfile:/home/jpai/business/jboss/wc/jbossas/projects/ejb3/trunk/nointerface/src/test/resources/deployers/
which shows me whether the deployer was considered relevant for the deployment
You can also see which deployers processed a deployment on the JMX console.
Find your (sub-)deployment/component in the jboss.deployment namespace. -
7. Re: AbstractVFSParsingDeployer doesn't kick in upon server r
heiko.braun Mar 5, 2009 5:59 AM (in response to heiko.braun)
You can also see which deployers processed a deployment on the JMX console.
Find your (sub-)deployment/component in the jboss.deployment namespace.
thanks, that's good to know