Remember that you have to configure your web context app1 to
allow cross-context access. If you have not done so, the method
you call below will always return null.
So your context xml file should look similar to this here:
Context docBase=YOUR_DOC_BASE crossContext=true/
I.e. the parameter
Using the load-on-startup mechanism was the way to go with older
servlet APIs. Nowadays, with servlet API 2.4, having a class
implement the ServletContextListener interface is better in my eyes.
Here you go:
public class MyInitClass implements ServletContextListener
{
static {
in an init class.
(Agreed, this is not a major problem, but i like to keep
things as small and simple as possible, and a class that
*can* serve web requests should also actually be used for
this purpose.)
Robert
Robert Graf-Waczenski a écrit :
Using the load-on-startup mechanism was the way to go
If I generate a dump of the JVM using Ctrl-Break while
running Tomcat as a console app, what's the best resource for
interpreting this? I suspect the problem is a thread
deadlock, or something similar.
This tells us that you succeed in getting a JVM thread dump and
you are asking for help
OK. Well, feel free to attach your stack dump then. Some curious
soul (including myself if i had the time) may either see the
problem immediately or use your own stack trace to guide you
through it.
Robert
-Original Message-
From: David Boyer [mailto:[EMAIL PROTECTED]
Sent: Tuesday,
. Your timeis deeply appreciated.
What I'd like to know is: do I have to do it in every
JSP (I have hundreds). And is there a configuration
solution as was alluded by Bill previously?
Once again, very many thanks!!!
Dola
--- Robert Graf-Waczenski [EMAIL PROTECTED] wrote:
Hi!
First
