If I remember well, redeploying/undeploying an exploded EAR didn't work reliably (certainly on Windows), because of locks, ...
But we preferred to live with it, because for a relative large EAR (about 80Mb, mostly from a 65M WAR), the time to unpack it was longer than the JBoss boot time on our hardware.
And you often have problems with statics anyway.
So I think "temp even for exploded" is not a good option, because it will defeat one of the purposes of using exploded deployments: speed.
Francois
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224016#4224016
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224016
"jaikiran" wrote : (i don't exactly remember where this logic resides, but i strongly believe its somewhere within tomcat/jboss web code).
|
For those curious, when the jsp is being serviced, the call goes through org.apache.jasper.compiler.Compiler:
/**
| * Determine if a compilation is necessary by checking the time stamp of the
| * JSP page with that of the corresponding .class or .java file. If the page
| * has dependencies, the check is also extended to its dependeants, and so
| * on. This method can by overidden by a subclasses of Compiler.
| *
| * @param checkClass
| * If true, check against .class file, if false, check against
| * .java file.
| */
| public boolean isOutDated(boolean checkClass)
|
|
Not sure about xhtml.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224010#4224010
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224010
"jaikiran" wrote : "gozilla" wrote : AFAIK, JBoss 4 only temped packed deployments like ears, wars, sars, ...
|
| That's correct. For exploded deployments (of WAR, EAR etc...) there were no temps in 4.x. I just did a simple test against the exploded jmx-console.war that comes in AS 4.x. There are no temps created for this app.
|
Hmmm, this then raises another question.
How did we then handle resources lookup at undeploy (when the app was deleted)?
I guess we didn't. :-)
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224008#4224008
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224008
"gozilla" wrote : AFAIK, JBoss 4 only temped packed deployments like ears, wars, sars, ...
That's correct. For exploded deployments (of WAR, EAR etc...) there were no temps in 4.x. I just did a simple test against the exploded jmx-console.war that comes in AS 4.x. There are no temps created for this app.
As for how the jsp changes are picked up in exploded deployments (on AS4.x), from what i remember - the timestamp of the jsp file is compared against the generated servlet classes (i don't exactly remember where this logic resides, but i strongly believe its somewhere within tomcat/jboss web code). I guess the same logic applies for xhtml files, not sure.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224007#4224007
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224007