RE: html:option and the 65k wall

[Danny Collins]

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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]

Sent: Thursday, January 24, 2002 8:18 PM
To: Struts Users Mailing List; [EMAIL PROTECTED]
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
=

...

...

...

...

B.jsp
=

...

 
 
 ...

...

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
 tag in place of many  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:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

RE: html:option and the 65k wall

[Cakalic, James]

Sorry if I'm arriving a little late to this thread. And I may be about to
show level of JSP ignorance but ...

It was my understanding that the 64K code limit was not the size of the
class but the bytecode size of any one method. Normally, the JSP compiler
generates a servlet that puts all of the code for your JSP expressions and
scriptlets in the _jspService method. This method corresponds to the body of
the JSP page.

In contrast, JSP also specifies a declaration syntax using <%! %> which
supports declaration of variables and, in fact, methods which will be
generated into the servlet outside the _jspService method. 

Best regards,
Jim Cakalic

> -Original Message-
> From: Barr, Scott [IBM GSA] [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, January 24, 2002 5:12 PM
> To: 'Struts Users Mailing List'
> Subject: RE: html:option and the 65k wall
> 
> 
> 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]>


Confidentiality Warning:  This e-mail contains information intended 
only for the use of the individual or entity named above.  If the reader of this 
e-mail is not the intended recipient or the employee or agent responsible for 
delivering it to the intended recipient, any dissemination, publication or copying of 
this e-mail is strictly prohibited. The sender does not accept any responsibility for 
any loss, disruption or damage to your data or computer system that may occur while 
using data contained in, or transmitted with, this e-mail.   If you have received this 
e-mail in error, please immediately notify us by return e-mail.  Thank you.

RE: html:option and the 65k wall

[Stephen Owens]

Danny,

What we've done in the past is to use the html:options tag instead of
html:option. That way you have one custom tag per set of options, rather
than one per option, it's way more efficient. If you search the list
archive you'll find some examples of using it.

regards,

Stephen Owens
Corner Software

> -Original Message-
> From: Danny Collins [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, January 24, 2002 5:10 PM
> 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:   
For additional commands, e-mail: 

RE: html:option and the 65k wall

[Jack Zakarian]

Hi
This is exactly the solution I was looking for. I am
new to struts and would appreciate if you could provide
some examples of how this is done.  I mean not only the
call to the popup but how to populate it and return the
selected data.

Thanks Jack

[EMAIL PROTECTED]

-Original Message-
From: Barr, Scott [IBM GSA] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 24, 2002 5:12 PM
To: 'Struts Users Mailing List'
Subject: RE: html:option and the 65k wall


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]>

RE: html:option and the 65k wall

[Barr, Scott [IBM GSA]]

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:   
For additional commands, e-mail: 

RE: html:option and the 65k wall

[Danny Collins]

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:[EMAIL PROTECTED]] 
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:
<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]>

Re: html:option and the 65k wall

[martin . cooper]

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
=

...

...

...

...

B.jsp
=

...

 
 
 ...

...

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 
 tag in place of many  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:   
For additional commands, e-mail: 

Re: html:option and the 65k wall

[Ted Husted]

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:   
For additional commands, e-mail: 

Re: html:option and the 65k wall

[Arron Bates]

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:   
>For additional commands, e-mail: 
>
>



--
To unsubscribe, e-mail:   
For additional commands, e-mail: