-
1. Re: Redeployment on JBoss 5
iradix Sep 25, 2008 9:19 PM (in response to 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 pages and I'd rather not have an update of them cause a redeploy. Is there any way to restrict it to only web.xml?
-
2. Re: Redeployment on JBoss 5
jaikiran Sep 26, 2008 2:27 AM (in response to iradix)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.
-
3. Re: Redeployment on JBoss 5
jaikiran Sep 26, 2008 2:37 AM (in response to iradix)"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 http://www.jboss.com/index.html?module=bb&op=viewtopic&t=138457
For example: Your application is an EAR file containing a WAR file, then the META-INF/application.xml of the EAR and the WEB-INF/web.xml of the war are both watched for changes. -
4. Re: Redeployment on JBoss 5
alesj Sep 26, 2008 5:38 AM (in response to iradix)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. -
5. Re: Redeployment on JBoss 5
iradix Sep 26, 2008 9:02 AM (in response to 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 keeping page (JSP, etc) files within WEB-INF (Spring comes to mind). If any change to those files causes a redeployment it's going to be an issue for people during development. -
6. Re: Redeployment on JBoss 5
alesj Sep 26, 2008 9:13 AM (in response to iradix)"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 fair number of web frameworks that suggest keeping page (JSP, etc) files within WEB-INF (Spring comes to mind). If any change to those files causes a redeployment it's going to be an issue for people during development.
I see.
This was an initial fix to the metadata update problem / legacy behavior.
So, filter definitely makes sense:
- https://jira.jboss.org/jira/browse/JBAS-5998 -
7. Re: Redeployment on JBoss 5
iradix Sep 26, 2008 9:30 AM (in response to 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 *.jsp, *.xhtml and other non-config files deployed to the WEB-INF folder.
-
8. Re: Redeployment on JBoss 5
alesj Sep 26, 2008 10:03 AM (in response to iradix)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. -