[jboss-user] [Microcontainer] - Re: Redeployment on JBoss 5

2008-09-26 Thread jaikiran
jaikiran wrote : As far as i know, its only the top level deployment descriptors that are watched for redeployment. Just to be more clear - If you have nested deployments then the top level deployment descriptor of each deployment is watched. See this for details

[jboss-user] [Microcontainer] - Re: Redeployment on JBoss 5

2008-09-26 Thread jaikiran
As far as i know, its only the top level deployment descriptors that are watched for redeployment. So for a war file its just the WEB-INF/web.xml which is watched for changes. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4178961#4178961 Reply to the post :

[jboss-user] [Microcontainer] - Re: Redeployment on JBoss 5

2008-09-26 Thread alesj
We check every metadata file in deployment + all sub-deployments: - http://anonsvn.jboss.org/repos/jbossas/trunk/system/src/main/org/jboss/system/server/profile/basic/MetaDataAwareProfile.java - https://jira.jboss.org/jira/browse/JBAS-4545 I guess I can add some filter to the check. View the

[jboss-user] [Microcontainer] - Re: Redeployment on JBoss 5

2008-09-26 Thread iradix
Ales, So if I understand this correctly getMetaDataLocations for a WAR deployment returns the WEB-INF folder, and the isModified method will check every child within that folder? That does seem to be somewhat undesirable. I know that there are a fair number of web frameworks that suggest

[jboss-user] [Microcontainer] - Re: Redeployment on JBoss 5

2008-09-26 Thread alesj
iradix wrote : | So if I understand this correctly getMetaDataLocations for a WAR deployment returns the WEB-INF folder, and the isModified method will check every child within that folder? | Yes. iradix wrote : | That does seem to be somewhat undesirable. I know that there are a

[jboss-user] [Microcontainer] - Re: Redeployment on JBoss 5

2008-09-26 Thread iradix
Cool. Off the top of my head, defaulting the filter to *.xml might be a good compromise. It seems to me like that would encompass the JBoss config files, standard JEE config files, and also web framework files that do necessitate a restart (Seam's components.xml for instance) while excluding

[jboss-user] [Microcontainer] - Re: Redeployment on JBoss 5

2008-09-26 Thread alesj
I've committed the change to the JBossAS trunk. By default it now includes .xml files only. But this can be changed in profile.xml configuration file. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4179084#4179084 Reply to the post :

[jboss-user] [Microcontainer] - Re: Redeployment on JBoss 5

2008-09-26 Thread iradix
Thank you Ales. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4179134#4179134 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4179134 ___ jboss-user mailing list

[jboss-user] [Microcontainer] - Re: Redeployment on JBoss 5

2008-09-25 Thread iradix
Just to clarify, after watching a bit more closely, it seems like it is a facelts template file (default.xhtml) located in WEB-INF/templates that changes and triggers a reload. There are non-configuration files that I tend to keep within WEB-INF just because they are not directly accessible