Scott, it's not a data delivery question, but the fact that Java wont
run a class over 64K.
...but what you recommend is cool, I've done apps like that myself.
Most cool. :)
Danny, it really is a case of optimising stuff until the class size is
down Apollo 13 style. Any Javascript, get that into its own .js file,
same with CSS.
Then there's the efficiency of the markup of the tags. The more logic
you get of the tags to do things, the less code there is in the servlet.
Last resort... are there any headers or footers which can be put into
their own JSP and dynamically include them?...
It's just little fiddly stuff like that.
Arron.
Barr, Scott [IBM GSA] wrote:
>Hi Danny
>
>When using large lists in previous projects, I have used url that generate
>popup windows from which you can do searches on relevant data.
>The user would do their search in the popup, select the item they wanted.
>Clicking OK would the populate the parent form with the data, and close the
>popup window.
>Worked very well, and saved delivering large amounts of data to the client
>
>Just a suggestion :)
>Scott Barr
>
>
>>-----Original Message-----
>>From: Danny Collins [SMTP:[EMAIL PROTECTED]]
>>Sent: Friday, January 25, 2002 8:40 AM
>>To: [EMAIL PROTECTED]
>>Subject: html:option and the 65k wall
>>
>>Hello all,
>> I have a jsp page that has a ton of very long option lists.
>>These are all generated dynamically from the DB. The problem is, if we
>>try to use the html:option tag we exceed 65k. What I would like to do is
>>move each html:select with all of it's generated options into it's own
>>jsp and just include all of the jsps on the main page. The problem with
>>that is the html:select's are mapped to the form class and I can't seem
>>to be able to figure out the syntax to be able to get to the form using
>>the html:select and html:options on an included page.
>> We did try to use the jsp:useBean with the FormClass on the
>>included page but that didn't seem to help. So either the included pages
>>are being compiled first so the form isn't in the request yet or we have
>>the syntax all wrong.
>>
>>Any suggestions?
>>
>>Danny Collins
>>
>
>--
>To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
>For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
