We ran into this exact problem, only we use ATG Dynamo. We had a tediously long line
of <html:option> tags -- over a hundred of them, actually (we were Struts-naive at the
time) -- and it was causing the page to bomb at runtime with an error about the 64k
limit. The problem laid in the JSP --> Java interpreter, which translates custom tags
so that every tag has its code placed inside the _jspService() method in the resulting
.java file. (Jasper [Tomcat's interpreter] alleviates this problem somewhat by giving
each custom tag a private method, instead of inlining the tag code.)
The most expedient way to eliminate this problem is to reduce the amount of custom
tags in your page, something that is desirable for reasons other than just those in
discussion here. To do this, I placed the items to be displayed in our <html:select>
box into a request-scoped List of LabelValueBeans. Our code went from this:
<html:select property="departureDay">
<html:option value="1">1</html:option>
<html:option value="2">2</html:option>
<html:option value="3">3</html:option>
[... etc, on up to 31 ...]
</html:select>
To this:
<html:select property="departureDay" onchange="calcBothDates(this.form);" >
<html:options collection="days" property="value" labelProperty="label" />
</html:select>
The code to do this in the Action is something like this:
List months = new ArrayList();
months.add(new LabelValueBean("January", 0);
months.add(new LabelValueBean("Februrary", 1);
// [... etc ...]
request.setAttribute("months", months);
Easy breezy, Japanezy!
HTH,
-= J
> -----Original Message-----
> From: David Thielen [mailto:[EMAIL PROTECTED]
> Sent: Thursday, August 14, 2003 8:37 AM
> To: Struts Users Mailing List
> Subject: Re: Code of a method longer than 65535 bytes
>
>
> I'm using JRun 4 - and need it for the EJB support so
> Tomcat's out. I also
> use [EMAIL PROTECTED] file="countries.jsp"% to pull the countries in.
> But regardless
> of how they are pulled in, they will be expanded within the
> form to be the
> actual select text.
>
> I guess I'll push Macromedia to eliminate the 64K limit.
>
> thanks - dave
>
>
> ----- Original Message -----
> From: "Craig R. McClanahan" <[EMAIL PROTECTED]>
> To: "Struts Users Mailing List" <[EMAIL PROTECTED]>;
> <[EMAIL PROTECTED]>
> Sent: Thursday, August 14, 2003 12:31 AM
> Subject: RE: Code of a method longer than 65535 bytes
>
>
> > On Thu, 14 Aug 2003, Suresh Addagalla wrote:
> >
> > > Date: Thu, 14 Aug 2003 10:33:38 +0530
> > > From: Suresh Addagalla <[EMAIL PROTECTED]>
> > > Reply-To: Struts Users Mailing List
> <[EMAIL PROTECTED]>,
> > > [EMAIL PROTECTED]
> > > To: 'Struts Users Mailing List' <[EMAIL PROTECTED]>
> > > Subject: RE: Code of a method longer than 65535 bytes
> > >
> > >
> > > Hello Criag,
> > >
> > > > * Use a JSP page compiler that doesn't make page developers deal
> > > > with the 64k limit problem (like Tomcat 4.1 or 5.0).
> > >
> > > I am using Tomcat 4.1.12 on Windows, and I got this
> problem. If any one
> > > has a clear idea on the min version of Tomcat I should
> use to get rid of
> > > this problem, please let me know.
> > >
> >
> > Jasper2 was introduced around 4.1.18 or so, so anything
> later than that
> > would be a good bet. The current production version is 4.1.27.
> >
> > But for the particular case of lots of countries being used
> twice, you
> > should really really really be using <html:options> no matter what
> > container you run on, so that updates to the list only have
> to happen in
> > one place rather than two.
> >
> > > Thanks,
> > > Suresh
> >
> > Craig
> >
> > PS: If you're currently using a Jasper1 based Tomcat,
> you'll also be very
> > pleased with the performance improvements in rendering
> speed for Jasper2
> > compiled JSP pages.
> >
> >
> >
> ---------------------------------------------------------------------
> > 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]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
