By the way, it used to work with jrun 2.3.3


-----Message d'origine-----
De : Sylvain Roche <[EMAIL PROTECTED]>
� : JRun-Talk <[EMAIL PROTECTED]>
Date : vendredi 3 novembre 2000 11:27
Objet : auto reloading a chained servlet


>Hi
>
>I've got an application, where a first servlet dispaches requests between
>different servlets, in charge of the business logic.
>Independantly, each servlet is reloaded on modification. ie, when a second
>stage servlet (business logic) is recompiled and directly accessed, it is
>reloaded. But when it is modified, and accessed through the dispatcher
>servlets, no verification is made to see if the version is newer than the
>one in memory, and the former version is executed.
>
>Is this normal ? and is there � way the work this out, in order to execute
>the last version servlet in both cases ?
>
>Regards
>Sylvain
>
>______________________________________________
>Sylvain Roche
>Responsable d�veloppement
>Add-Online
>www.add-online.fr
>
>80 rue d'Alsace
>69100 VILLEURBANNE
>France
>
>tel : +33 437431260
>fax: +33 437431269
>
>---------------------------------------------------------------------------
---
>Archives: http://www.egroups.com/group/jrun-interest/
>Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebaror send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the
body.

------------------------------------------------------------------------------
Archives: http://www.egroups.com/group/jrun-interest/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebarRsts&bodyRsts/jrun_talk
or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the 
body.

Reply via email to