Well, of course the stack will be container-specific =) In WebLogic, the
exception will be something like com.weblogic.blah.foo with a different
message. The exception message there seemed descriptive enough to debug.
- r
> -----Original Message-----
> From: Kenneth Litwak [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, August 15, 2001 7:09 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Newbie help needed: error running JSP
>
>
> Rob S. wrote:
> ot to be a jerk or anything, your "newbie help"
> questions are fine and all,
> but the problem is that the only connection they
> have to Tomcat is that
> you're using the container.
>
> It's like if I emailed the GCC or Visual Studio
> lists saying, "how come I'm
> getting all of these memory leaks in my
> programs?" See what I'm saying?
> You really should pick up a book on JSPs /
> Servlets...
>
> Rob, I understand your point. The reason I posted
> here is that the stack trace appears to me completley
> unique to Tomcat. Weblogic might produce totally
> different information, as might Websphere as might the
> J2EE RI. I don't know what from the stack trace is
> unique to Tomcat, and therefore a config error I've
> made, and what is common to all JSP engines. How do
> you know the diference? Thanks.
>
> Ken
>
> __________________________________________________
> Do You Yahoo!?
> Make international calls for as low as $.04/minute with Yahoo! Messenger
> http://phonecard.yahoo.com/
>
