"jean-frederic clere" <[EMAIL PROTECTED]> wrote:
> Pier Fumagalli wrote:
>>
>> "Remy Maucherat" <[EMAIL PROTECTED]> wrote:
>>
>>> Thanks for the report Pier. I had been wondering for AGES why the CL would
>>> reload the webapp "randomly" after accessing a JSP, telling that a bean
>>> class had been modified. I couldn't find a reason why it was a bug (the
>>> logging I added to investigate this displayed different dates which didn't
>>> appear bogus), but I failed to undestand why it happened.
>>
>> Yeah, I wonder why noone actually noticed this before... Am I the only idiot
>> using TC4 in a secure production environment? (Meaning, chrooted JVM and
>> suid execution, with access only to the "work" directory)?
>
> Last time I have tried this I noted that it did not work: TC tries to
> write in several places (at least conf and webapps).
Conf works... I'll never give him access to my configurations directory...
:) One trick is _never_ to put any source .java file anywhere in the WEB-INF
directory, so that the "useBean" thing won't try to compile them (or at
least, it seems to be working this way)
Pier
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
