Re: [jboss-as7-dev] Changes to .jsp in an exploded deployment no longer picked up?
The default for JSF is production mode. JSF actually has four modes,
"Development", "UnitTest", "SystemTest", and
"Production". But
"Development" and "Production" are the only ones used by the JSF impl.
Usually, the developer would set this as a context param in web.xml.
It can also be set via JNDI.
As I was pointing out earlier, Development mode for JSF Facelets xhtml
files acts like JSP. We need to support exploded deployment to make
it worthwhile.
Stan
Quoting Max Rydahl Andersen <max.andersen(a)redhat.com>:
>
> Well, everything can be easily updated, like static files, and there are
> plenty of dynamic pages tech out there. JSP is actually not dynamic
> because it uses compilation, although this is hidden, they are actually
> servlets with a small runtime.
>
> There are plenty of possibilities for you:
> - Make your updates in place, then add a .dodeploy. That's more robust
> (it allows classes changes), and still far faster to use an exploded
> deployment.
How is that faster for anything but small examples ? it will
invalidate running sessions and require
bigger items (such as Hibernate/JPA, Spring configuration etc. to
have to restart too.)
> - Add the development mode in the JSP config if you're working with
> exploded deployments, and anticipate only JSP updates. Sorry, but this
> is a rather specific situation right now, it's no longer 2001.
If this is just for JSP compilation it is less of an issue.
Is JSF facelets refresh also disabled by default or will it be ?
/max
http://about.me/maxandersen
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev