Thank for the reply joe...
But the Tomcat I am using is 4.1 only.....I have checked the documentation
and found out that both Tomcat4.1 and Weblogic8.1 is conformant to J2EE1.3
( Servlet 2.3 / JSP 1.2 ) ....so the problem is not with the jsp specs....
further, i feel that the problem is with the mechanism with which the
container translates the JSP to servlet when the JSP is having tags....
On comparison of servlets I could find out that:
1. Weblogic generated servlet has a HUGE jspservice method. The size can be
attributed to all the EXTRA tag handling statements ( like getting a tag
object frm the tag pool, setting its attributes, calling its doStart()
etc... )
2. On the other hand, Tomcat generated a servlet with a much smaller
jspservice method. At each tag handling part, it just calls a method to
handle the tag. Those methods will also be generated by Tomcat in the
servlet. This definitely seems to be a smarter strategy.
Now, my question is whether we can configure Weblogic in some way to do
the translation as Tomcat does? ( I need to use Weblogic, thats a project
requirement )
Please help.
Thanks,
rahul
-----Original Message-----
From: Joe Germuska [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 18, 2004 6:57 PM
To: Struts Users Mailing List; struts
Subject: Re: FW: code too large for try statement
It just so happens that I just wrote an answer to in response to a
different email.
At 8:18 AM -0500 5/18/04, Joe Germuska wrote:
>
>It works find on Tomcat 5 because JSP 2.0 works around the maximum
>method-length limitation. Weblogic 8.1 is still J2EE 1.3 (Servlet
>2.3/JSP 1.2).
>
>I'd suggest using Tomcat 4 where you now use Tomcat 5 to minimize
>the likelihood of these kinds of surprises.
You are using Tomcat 5, aren't you?
Joe
--
Joe Germuska
[EMAIL PROTECTED]
http://blog.germuska.com
"Imagine if every Thursday your shoes exploded if you tied them
the usual way. This happens to us all the time with computers, and
nobody thinks of complaining."
-- Jef Raskin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
