You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@geronimo.apache.org by Hari Krishna Korrapati <ha...@gmail.com> on 2007/02/07 16:07:09 UTC

Hot Deployment in Geronimo

Hi,
       We are using geronimo1.1.1 application server.
After deploying the application, if particular file has been changed, then
we will replace the corresponding file in repository with the latest file
and restart the application.

In geronimo1.0 whenever we changed some JSP file, we never restarted the
application. We just replaced JSP in repository, and the application worked
fine without restarting the application. But in geronimo1.1.1, JSP's are not
being replaced without restarting the server.
Is it mandatory in geronimo1.1.1 to restart the application after changing
the JSP's in the repository. If not, whats the best way to update the file?

Is there any property need to be set in config file of geronimo...?

Could somebody please advice on the same issue.


-- 
Regards,
Hari

Re: Hot Deployment in Geronimo

Posted by Vamsavardhana Reddy <c1...@gmail.com>.
I have noticed this difference in behaviour between G1.0 and G1.1, but never
bothered to ask.  I never tested if the replaced JSP would be used after
restarting the app (or the server).  I guess this has something to do with
the JSP precompilation.

Vamsi

On 2/7/07, Hari Krishna Korrapati <ha...@gmail.com> wrote:
>
> Hi,
>        We are using geronimo1.1.1 application server.
> After deploying the application, if particular file has been changed, then
> we will replace the corresponding file in repository with the latest file
> and restart the application.
>
> In geronimo1.0 whenever we changed some JSP file, we never restarted the
> application. We just replaced JSP in repository, and the application worked
> fine without restarting the application. But in geronimo1.1.1, JSP's are
> not being replaced without restarting the server.
> Is it mandatory in geronimo1.1.1 to restart the application after changing
> the JSP's in the repository. If not, whats the best way to update the file?
>
> Is there any property need to be set in config file of geronimo...?
>
> Could somebody please advice on the same issue.
>
>
> --
> Regards,
> Hari

Re: Hot Deployment in Geronimo

Posted by Hari Krishna Korrapati <ha...@gmail.com>.
Hi paul,

          I am also using Geronimo with tomact only.
         I have updated the web.xml according to your instructions, its
working fine now.
Now i am able to see the changes made to JSP's without restarting the
server, which saves lots of time.

Thank you.


On 2/7/07, Paul McMahan <pa...@gmail.com> wrote:
>
> I'm not sure about the jetty assembly but as I recall in the
> geronimo-1.1.1 tomcat assembly you should be able to turn on this
> feature by editing var/catalina/conf/web.xml and changing this :
>         <init-param>
>             <param-name>development</param-name>
>             <param-value>false</param-value>
>         </init-param>
> to this
>         <init-param>
>             <param-name>development</param-name>
>             <param-value>true</param-value>
>         </init-param>
> for the jsp servlet.   In geronimo 1.0 that parameter was not
> specified and defaulted to true.
>
> Best wishes,
> Paul
>
> On 2/7/07, Hari Krishna Korrapati <ha...@gmail.com> wrote:
> > Hi,
> >         We are using geronimo1.1.1 application server.
> >  After deploying the application, if particular file has been changed,
> then
> > we will replace the corresponding file in repository with the latest
> file
> > and restart the application.
> >
> >  In geronimo1.0 whenever we changed some JSP file, we never restarted
> the
> > application. We just replaced JSP in repository, and the application
> worked
> > fine without restarting the application. But in geronimo1.1.1, JSP's are
> not
> > being replaced without restarting the server.
> >  Is it mandatory in geronimo1.1.1 to restart the application after
> changing
> > the JSP's in the repository. If not, whats the best way to update the
> file?
> >
> >  Is there any property need to be set in config file of geronimo...?
> >
> >  Could somebody please advice on the same issue.
> >
> >
> > --
> > Regards,
> > Hari
>



-- 
Regards,
Hari

Re: Hot Deployment in Geronimo

Posted by Paul McMahan <pa...@gmail.com>.
I'm not sure about the jetty assembly but as I recall in the
geronimo-1.1.1 tomcat assembly you should be able to turn on this
feature by editing var/catalina/conf/web.xml and changing this :
        <init-param>
            <param-name>development</param-name>
            <param-value>false</param-value>
        </init-param>
to this
        <init-param>
            <param-name>development</param-name>
            <param-value>true</param-value>
        </init-param>
for the jsp servlet.   In geronimo 1.0 that parameter was not
specified and defaulted to true.

Best wishes,
Paul

On 2/7/07, Hari Krishna Korrapati <ha...@gmail.com> wrote:
> Hi,
>         We are using geronimo1.1.1 application server.
>  After deploying the application, if particular file has been changed, then
> we will replace the corresponding file in repository with the latest file
> and restart the application.
>
>  In geronimo1.0 whenever we changed some JSP file, we never restarted the
> application. We just replaced JSP in repository, and the application worked
> fine without restarting the application. But in geronimo1.1.1, JSP's are not
> being replaced without restarting the server.
>  Is it mandatory in geronimo1.1.1 to restart the application after changing
> the JSP's in the repository. If not, whats the best way to update the file?
>
>  Is there any property need to be set in config file of geronimo...?
>
>  Could somebody please advice on the same issue.
>
>
> --
> Regards,
> Hari