-
From: QM [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 19, 2004 5:17 PM
To: Tomcat Users List
Subject: Re: RequestDispatcher resource not available
: The point is I won't be able to start the server frequently to add new
: servlets, because our company needs the service 24/7.
Under
: The point is I won't be able to start the server frequently to add new
: servlets, because our company needs the service 24/7.
Understood; please report your final solution, if possible.
Whenever an app steps out of the standard, there's an opportunity for
innovation. =)
One other idea: Tomcat
4 10:55 AM
>To: Tomcat Users List
>Subject: RE: RequestDispatcher resource not available
>
>Standard sun 1.4 jvm and a dualprocessor 1.5GHz, 1.5GB Ram Raid5 I
think
>Database is running on a sun dualprocessor speed and Ram I don't know.
>
>But we are considering a Su
From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 19, 2004 4:39 PM
To: Tomcat Users List
Subject: RE: RequestDispatcher resource not available
Hi,
>We are now for public pages that are cached as a whole down at 0.25
>seconds included the delivery. And really heavy gene
Hi,
>We are now for public pages that are cached as a whole down at 0.25
>seconds included the delivery. And really heavy generated pages (200 db
>queries) at
>1.5-2 seconds( I know there I have to do heavy optimisation)
Really? You do:
- Apache to Tomcat forwarding via mod_jk
- Tomcat WelcomeS
>>We want to add servlets in the running system, just by saying "now you
>>can"
>OK. That certainly narrows down your possibilities.
Drastically
>>The mappings are stored in the database but would be cached in the
>>servletContext and could be dynamically reloaded.
>Cool.
The application now c
Hola,
>We want to add servlets in the running system, just by saying "now you
can"
OK. That certainly narrows down your possibilities.
>The mappings are stored in the database but would be cached in the
>servletContext and could be dynamically reloaded.
Cool.
>I also thought about the invoke
: There lies the problem i don't know which servlets i would get, and i don't
: want to reconfigure the web.xml and restart the server every time something
: changes or get added.
If you want changes to be picked up w/o restarting the server, you'll
have to set "reloadable=true" for the context, w
Hi,
>There lies the problem i don't know which servlets i would get, and i
don't
>want to reconfigure the web.xml and restart the server every time
something
>changes or get added.
That's the standard practice.
>Could you describe your second point a little closer, please?
If you map a servlet
Hi,
- Define and map all your servlets in web.xml.
- Use the servlet-mapping url-pattern as your argument to the getRequestDisptcher call.
Yoav Shapira
Millennium Research Informatics
>-Original Message-
>From: Nitschke Michael [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, May 19, 2004 6:
10 matches
Mail list logo
