[jboss-dev-forums] [Design of POJO Server] - Re: AS 5 not reliably picking up changes in exploded EAR

[alesj]

"max.andersen at jboss.com" wrote : I still don't understand why Seam needs to have a tmp for exploded deployment ?
It's a very simple problem. ;-)

Some apps, in this case it was Seam Wicket example app,
still want to do some resources lookup at undeploy.
An undeploy which was triggered by the app's dir/archive deletion from deploy/.
But since the app was deleted there is nowhere to do the lookup from.
Unless you do a temp copy. ;-)
And this is what we used to do, and what most app servers still do.

We changed this behavior due to the VFS usage which can handle nested jars in memory.
But we still provide a way to do temp - via jboss-structure.xml.
In this case Seam guys found it to verbose to have to include jboss-structure.xml
in any Seam deployment in JBoss5, hence this feature was developed
== able to recognize deployments and modify the ContextInfo info before the actual/real deployment phase kicks in.

We did temps by-default before, in 4.x, but I don't know how 
Tomcat/JBossWeb handled this, since afaik WarDeployer didn't monitor all non-metadata files.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4217186#4217186

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4217186