Keeping the server side object alive !!! 2007-01-15 - By Andre Prasetya
Back
I attach an example for you.
MigrationUtil is a helper class that needs initialisation when the webapp
started and needs cleaning when the webapp stopped
On 1/16/07, Luis Rivera <luiggiilca@(protected)> wrote:
>
> Dear Leon,
>
> Thanks for the info, I am reading about Contexts, but I am not sure if
> they
> are created as soon as tomcat starts. This listener seems to be event
> based,
> as long as an event is auto generated after Tomcat has started, it would
> work, or if there is another mechanism that can be used to generate the
> event that is automatic and that does not require a request from the
> client,
> I think it might work.
>
> Thanks in advance,
> --Luis R.
>
> On 1/15/07, Leon Rosenberg <rosenberg.leon@(protected)> wrote:
> >
> > I think what you need is a ContextListener. With it, you will be
> > notified when the context (webapp) starts and can perform
> > initialization, and when the context is destroyed you can perform
> > de-initialization (stop your threads, cleanup ressources and such).
> >
> > regards
> > Leon
> >
> > On 1/15/07, Luis Rivera <luiggiilca@(protected)> wrote:
> > > Hi,
> > >
> > > I would like to know how could I jump start my web service in tomcat
> > before
> > > any call from the client is made. My first version only needed to be
> > > stateless and that worked fine, since I noticed that each call from
> the
> > > client creates a new object in the server. However, now I would like
> to
> > > create some threads because I have a custom administration module
> > > (session/security/database).
> > >
> > > I can create them when the first call is made (using statics), but I
> > would
> > > like to get rid of the overhead in the first call by somehow jump
> > starting
> > > the application to do the loading and initialization that the
> > application
> > > threads need to do, so that the when the first call is made, there is
> no
> > > overhead to pay.
> > >
> > > I am not sure. Is this possible? I am probably not understanding fully
> > the
> > > servlet model or how tomcat/axis is supposed to be stateful at the
> > server
> > > side.
> > >
> > > I guess, if there is a smarter way to do this without using
> > threads/statics
> > > I would like to know where I could find an example.
> > >
> > > Thanks in advance,
> > > --Luis R.
> > >
> > >
> >
> > -- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
> > To start a new topic, e-mail: users@(protected)
> > To unsubscribe, e-mail: users-unsubscribe@(protected)
> > For additional commands, e-mail: users-help@(protected)
> >
> >
>
>
--
-Andre-
People see things the way they are and say "why ?" I see things that never
were and say "Why not ?"
I attach an example for you.<br><br>MigrationUtil is a helper class that needs
initialisation when the webapp started and needs cleaning when the webapp
stopped<br><br><div><span class="gmail_quote">On 1/16/07, <b class="gmail
_sendername">
Luis Rivera</b> <<a href="mailto:luiggiilca@(protected)">luiggiilca@(protected)<
/a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px
solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Dear Leon,<br><br>Thanks for the info, I am reading about Contexts
, but I am not sure if they<br>are created as soon as tomcat starts. This
listener seems to be event based,<br>as long as an event is auto generated
after Tomcat has started, it would
<br>work, or if there is another mechanism that can be used to generate the<br
>event that is automatic and that does not require a request from the client,<br
>I think it might work.<br><br> Thanks in advance,<br>
--Luis R.
<br><br>On 1/15/07, Leon Rosenberg <<a href="mailto:rosenberg.leon
@(protected)">rosenberg.leon@(protected)</a>> wrote:<br>><br>> I
think what you need is a ContextListener. With it, you will be<br>> notified
when the context (webapp) starts and can perform
<br>> initialization, and when the context is destroyed you can perform<br>
> de-initialization (stop your threads, cleanup ressources and such).<br>>
<br>> regards<br>> Leon<br>><br>> On 1/15/07, Luis Rivera <
<a href="mailto:luiggiilca@(protected)">luiggiilca@(protected)</a>> wrote:<br>
> > Hi,<br>> ><br>> > I would like to
know how could I jump start my web service in tomcat<br>> before<br>> >
; any call from the client is made. My first version only needed to be
<br>> > stateless and that worked fine, since I noticed that each call
from the<br>> > client creates a new object in the server. However, now I
would like to<br>> > create some threads because I have a custom
administration module
<br>> > (session/security/database).<br>> ><br>> > I can
create them when the first call is made (using statics), but I<br>> would<br
>> > like to get rid of the overhead in the first call by somehow jump
<br>> starting<br>> > the application to do the loading and
initialization that the<br>> application<br>> > threads need to do, so
that the when the first call is made, there is no<br>> > overhead to pay.
<br>> ><br>> > I am not sure. Is this possible? I am probably not
understanding fully<br>> the<br>> > servlet model or how tomcat/axis
is supposed to be stateful at the<br>> server<br>> > side.
<br>> ><br>> > I guess, if there is a smarter way to do this
without using<br>> threads/statics<br>> > I would like to know where I
could find an example.<br>> ><br>> > Thanks
in advance,
<br>> > --Luis R.<br>> ><br>> ><br>>
;<br>> -- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
<br>> To start a new topic, e-mail: <a href="mailto:users@(protected)"
>users@(protected)
</a><br>> To unsubscribe, e-mail: <a href="mailto:users-unsubscribe@(protected)
.apache.org">users-unsubscribe@(protected)</a><br>> For additional
commands, e-mail: <a href="mailto:users-help@(protected)">users-help
@(protected)
</a><br>><br>><br><br></blockquote></div><br><br clear="all"><br>-- <br>
-Andre-<br><br>People see things the way they are and say "why ?" I
see things that never were and say "Why not ?"
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To start a new topic, e-mail: users@(protected)
To unsubscribe, e-mail: users-unsubscribe@(protected)
For additional commands, e-mail: users-help@(protected)
|
|
