Re: [jboss-as7-dev] Changes to .jsp in an exploded deployment no longer picked up?
On Tue, 2011-04-26 at 13:49 +0200, Max Rydahl Andersen wrote:
You would rather have the server out of the box be TCK compliant
than usable for development ? I thought we were pass the mistakes
made in latest AS and EAP being targeted purely for production ?
The dev scenario I described using a marker (or the equivalent API call
to trigger a redeploy) seems far more sustainable, even if it takes a
bit more time (framework init, etc).
> The domain is a centralized config, fully documented, dynamic,
so it
> should more practical to use than the previous files. I understand
> there's an initial learning period, but it should be worth it.
I'm sorry, but that's just not making sense to me.
And btw. where is the documentation for that AS 7 setting ?
And which other flags need to be enabled for other subsystems to have
"development"
enabled ?
JSP is a bit specific, and I explained why.
Hopefully. Development mode for JSPs is a relic of the past, deprecated
if you prefer. So it is enabled back using a flag, for the folks that
were really in love with it back then, and still use straight JSPs. This
flag is JSP specific. Looking at your new email: facelets are not JSPs.
--
Remy Maucherat <rmaucher(a)redhat.com>
Red Hat Inc