You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@struts.apache.org by Danny Collins <dc...@maine.rr.com> on 2002/01/24 23:10:03 UTC
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
RE: html:option and the 65k wall
Posted by Danny Collins <dc...@maine.rr.com>.
Ted, thanks for the velocity stuff, I will check it out tonight.
Scott,
We tried the pop up approach but for some unknown reason our
users are insanely against the popups. Although they won't be if we end
up using the Javascript solution we have right now because even on big
beefy multiprocessor servers this particular page takes almost 45
seconds to load.
Arron,
I will definitely look into trying to slim down the jsp as much
as possible. There might still be some javascript that could be moved
and there is the possibility that some of the page could be moved into a
header and footer. Thanks for the input.
Thanks for the suggestions guys.
Oh, if anyone is wondering, this is for a production system that has
been developed in 5 months. We are replacing 3 disparate systems that
our users had to data entry 3 separate times and spent a lot of time
reconciling their data because they never seemed to be able to enter it
3 times the same way. It is mainly a data capture system that
communicates with some legacy systems on the mainframe and some old (
but still working ) microfocus cobol. Struts has been the only reason we
have been able to develop this as quickly as we have.
Thanks for the good work, I am looking forward to exploring what new
services are available in the new release.
Danny
-----Original Message-----
From: Ted Husted [mailto:husted@apache.org]
Sent: Thursday, January 24, 2002 8:06 PM
To: Struts Users Mailing List
Subject: Re: html:option and the 65k wall
Might be an interesting use-case for Velocity templates.
It's not an election of remedies; these can be used along side of JSPs
as needed. So you could just pop one in here, and then go back to JSPs.
http://husted.com/struts/resources/velstruts.zip
-- Ted Husted, Husted dot Com, Fairport NY USA.
-- Java Web Development with Struts.
-- Tel +1 585 737-3463.
-- Web http://www.husted.com/struts/
Danny Collins wrote:
>
> 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:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: html:option and the 65k wall
Posted by Ted Husted <hu...@apache.org>.
Might be an interesting use-case for Velocity templates.
It's not an election of remedies; these can be used along side of JSPs
as needed. So you could just pop one in here, and then go back to JSPs.
http://husted.com/struts/resources/velstruts.zip
-- Ted Husted, Husted dot Com, Fairport NY USA.
-- Java Web Development with Struts.
-- Tel +1 585 737-3463.
-- Web http://www.husted.com/struts/
Danny Collins wrote:
>
> 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: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: html:option and the 65k wall
Posted by Danny Collins <x1...@hotmail.com>.
Martin,
Really? Cool, I must have missed the optionS tag. I will look
into that. Hey you know what, I jst realized that I was doing a JSP
useBean for the same bean on the main jsp and the included jsp. Maybe
that was what was throwing the error!
Damn.
Thanks
Danny
-----Original Message-----
From: martin.cooper@tumbleweed.com [mailto:martin.cooper@tumbleweed.com]
Sent: Thursday, January 24, 2002 8:18 PM
To: Struts Users Mailing List; DMCollins@bigfoot.com
Subject: Re: html:option and the 65k wall
I'm not sure I understand the problem you are having in relation to the
form tag. I have several cases where I have select and option tags in a
JSP
page which is included within another JSP which actually contains the
form
tag. For example:
A.jsp
=====
...
<html:form ... >
...
<jsp:include page="B.jsp" flush="true" />
...
</html:form>
...
B.jsp
=====
...
<html:select ... >
<html:option ... />
<html:option ... />
...
</html:select>
...
This is not a problem. What kind of issues are you seeing?
Another possibility you might want to look at would be to use the
<html:options> tag in place of many <html:option> tags.
--
Martin Cooper
At 02:10 PM 1/24/02, Danny Collins wrote:
>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: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: html:option and the 65k wall
Posted by ma...@tumbleweed.com.
I'm not sure I understand the problem you are having in relation to the
form tag. I have several cases where I have select and option tags in a JSP
page which is included within another JSP which actually contains the form
tag. For example:
A.jsp
=====
...
<html:form ... >
...
<jsp:include page="B.jsp" flush="true" />
...
</html:form>
...
B.jsp
=====
...
<html:select ... >
<html:option ... />
<html:option ... />
...
</html:select>
...
This is not a problem. What kind of issues are you seeing?
Another possibility you might want to look at would be to use the
<html:options> tag in place of many <html:option> tags.
--
Martin Cooper
At 02:10 PM 1/24/02, Danny Collins wrote:
>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: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>