Re: Displaying is easy, capturing is not

2003-07-30 Thread Ajay Patil
Dear Rick,

I had implemented the JSP as follows:
The top part of JSP shows the search form.
The bottom part of JSP shows the results.

The  tag is used to show the results
(the bottom part is not displayed if the Results bean is NULL)

Initially, Results bean is NULL and user will see only the top
part (Search form).

When the user clicks on Search, the Results bean gets initialized,
and the user sees both Search and Results.

When the user clicks on "Reset", the Results bean is set to NULL.
The bottom part will disappear because of the  tag.

I had posted the code as an example yesterday. Please look in the
archives.

I hope that my above explanation is not ambigious.
Ajay

> Hi, guys:

> I have a list for user to select, when user select one
> item from the list, and hit search button, a results
> table will be displayed at the bottom half of the
> page. Now, if user selects another item from the list,
> I want to refresh the table (or page?) and make the
> results table disappear before user hit search button
> again. I have no idea to do this. Can anyone give some
> thoughts on this?

> regards,
> rick


Ajay Patil
Vertex Software Pvt. Ltd.
[EMAIL PROTECTED]
http://www.vertex.co.in




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Displaying is easy, capturing is not..

2003-07-30 Thread Yee, Richard K,,DMDCWEST
Mona,
You might consider first displaying the values and providing an edit button
next to the values. If the user presses the edit button, then the row is
displayed as editable fields.
Another solution might be to use check boxes to select which rows should be
edited and then present only those rows (limiting it to a reasonable number)
on the next page to edit. Look at how a web mail application works.

Regards,

Richard


-Original Message-
From: Alawadhi, Mona [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, July 30, 2003 11:36 AM
To: 'Struts Users Mailing List'
Subject: RE: Displaying is easy, capturing is not..


Thank you - I am definately considering that. I'll probably limit the user.

-Original Message-
From: Yee, Richard K,,DMDCWEST [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 30, 2003 2:04 PM
To: 'Struts Users Mailing List'
Subject: RE: Displaying is easy, capturing is not..


Mona,
I don't think the user's browser will handle many more than 50 (a guess)
much less 600 text input elements on a single page. I think you should
re-think the UI so that fewer input elements are needed. Handling 600 input
fields on the server side will take a long time (several seconds to a few
minutes).

-Richard

-Original Message-
From: atta-ur rehman [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, July 30, 2003 10:50 AM
To: Struts Users Mailing List
Subject: Re: Displaying is easy, capturing is not..


Hello Mona,

is ABC is bean that has six properties that you need to show? and then you
have a collection of ABC objects in a List or Vector? if so, you can use the
indexed properties to capture all the changes done on the page.

and yes, usually one submit button is enough for six hundred values!!!

ATTA

- Original Message - 
From: "Alawadhi, Mona" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Sent: Wednesday, July 30, 2003 10:32 AM
Subject: Displaying is easy, capturing is not..


> Hello Everyone,
>
> I wonder if someone can help me with this problem. I would appreciate
> any smart suggestion.
>
> I have a JSP that displays a collection (ValueObject fields) Let's
> call
the
> collection ABC - it consists of 6 items. I might have more than one
> ABC collections to display. This can be done by setting a Vector which
consists
> of a number of ABC collections, and simply I can iterate through the
Vector
> in my JSP and display all the ABC collections I have using textboxes.
>
> When the user tries to change any of those textboxes, I should be able
> to capture them. I have one submit button that I am using, and if, for
example,
> I have two ABC's there, I should be able to capture all 12 items.
> (note
that
> I might have 100 ABCs, in which case I have to capture 600 items.)
>
> How can I do that using one submit button?
>
> Thank you in advance,
>
> Mona
>
>
>
>
>

*
> The information in this email is confidential and may be legally
privileged.
> It is intended solely for the addressee. Access to this email by
> anyone
else
> is unauthorized.
>
> If you are not the intended recipient, any disclosure, copying,
distribution
> or any action taken or omitted to be taken in reliance on it, is
prohibited
> and may be unlawful. When addressed to our clients any opinions or
> advice contained in this email are subject to the terms and conditions 
> expressed
in
> the governing KPMG client engagement letter.
>

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



*
The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorized. 

If you are not the intended recipient, any disclosure, copying, distribution
or any action taken or omitted to be taken in reliance on it, is prohibited
and may be unlawful. When addressed to our clients any opinions or advice
contained in this email are subject to the terms and conditions expressed in
the governing KPMG client engagement letter. 

*


--

RE: Displaying is easy, capturing is not..

2003-07-30 Thread Alawadhi, Mona
Thank you - I am definately considering that. I'll probably limit the user.

-Original Message-
From: Yee, Richard K,,DMDCWEST [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 30, 2003 2:04 PM
To: 'Struts Users Mailing List'
Subject: RE: Displaying is easy, capturing is not..


Mona,
I don't think the user's browser will handle many more than 50 (a guess)
much less 600 text input elements on a single page. I think you should
re-think the UI so that fewer input elements are needed. Handling 600 input
fields on the server side will take a long time (several seconds to a few
minutes).

-Richard

-Original Message-
From: atta-ur rehman [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, July 30, 2003 10:50 AM
To: Struts Users Mailing List
Subject: Re: Displaying is easy, capturing is not..


Hello Mona,

is ABC is bean that has six properties that you need to show? and then you
have a collection of ABC objects in a List or Vector? if so, you can use the
indexed properties to capture all the changes done on the page.

and yes, usually one submit button is enough for six hundred values!!!

ATTA

- Original Message - 
From: "Alawadhi, Mona" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Sent: Wednesday, July 30, 2003 10:32 AM
Subject: Displaying is easy, capturing is not..


> Hello Everyone,
>
> I wonder if someone can help me with this problem. I would appreciate 
> any smart suggestion.
>
> I have a JSP that displays a collection (ValueObject fields) Let's 
> call
the
> collection ABC - it consists of 6 items. I might have more than one 
> ABC collections to display. This can be done by setting a Vector which
consists
> of a number of ABC collections, and simply I can iterate through the
Vector
> in my JSP and display all the ABC collections I have using textboxes.
>
> When the user tries to change any of those textboxes, I should be able 
> to capture them. I have one submit button that I am using, and if, for
example,
> I have two ABC's there, I should be able to capture all 12 items. 
> (note
that
> I might have 100 ABCs, in which case I have to capture 600 items.)
>
> How can I do that using one submit button?
>
> Thank you in advance,
>
> Mona
>
>
>
>
>

*
> The information in this email is confidential and may be legally
privileged.
> It is intended solely for the addressee. Access to this email by 
> anyone
else
> is unauthorized.
>
> If you are not the intended recipient, any disclosure, copying,
distribution
> or any action taken or omitted to be taken in reliance on it, is
prohibited
> and may be unlawful. When addressed to our clients any opinions or 
> advice contained in this email are subject to the terms and conditions 
> expressed
in
> the governing KPMG client engagement letter.
>

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


*
The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorized. 

If you are not the intended recipient, any disclosure, copying, distribution
or any action taken or omitted to be taken in reliance on it, is prohibited
and may be unlawful. When addressed to our clients any opinions or advice
contained in this email are subject to the terms and conditions expressed in
the governing KPMG client engagement letter. 
*


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Displaying is easy, capturing is not..

2003-07-30 Thread Yee, Richard K,,DMDCWEST
Mona,
I don't think the user's browser will handle many more than 50 (a guess)
much less 600 text input elements on a single page. I think you should
re-think the UI so that fewer input elements are needed. Handling 600 input
fields on the server side will take a long time (several seconds to a few
minutes).

-Richard

-Original Message-
From: atta-ur rehman [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, July 30, 2003 10:50 AM
To: Struts Users Mailing List
Subject: Re: Displaying is easy, capturing is not..


Hello Mona,

is ABC is bean that has six properties that you need to show? and then you
have a collection of ABC objects in a List or Vector? if so, you can use the
indexed properties to capture all the changes done on the page.

and yes, usually one submit button is enough for six hundred values!!!

ATTA

- Original Message - 
From: "Alawadhi, Mona" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Sent: Wednesday, July 30, 2003 10:32 AM
Subject: Displaying is easy, capturing is not..


> Hello Everyone,
>
> I wonder if someone can help me with this problem. I would appreciate 
> any smart suggestion.
>
> I have a JSP that displays a collection (ValueObject fields) Let's 
> call
the
> collection ABC - it consists of 6 items. I might have more than one 
> ABC collections to display. This can be done by setting a Vector which
consists
> of a number of ABC collections, and simply I can iterate through the
Vector
> in my JSP and display all the ABC collections I have using textboxes.
>
> When the user tries to change any of those textboxes, I should be able 
> to capture them. I have one submit button that I am using, and if, for
example,
> I have two ABC's there, I should be able to capture all 12 items. 
> (note
that
> I might have 100 ABCs, in which case I have to capture 600 items.)
>
> How can I do that using one submit button?
>
> Thank you in advance,
>
> Mona
>
>
>
>
>

*
> The information in this email is confidential and may be legally
privileged.
> It is intended solely for the addressee. Access to this email by 
> anyone
else
> is unauthorized.
>
> If you are not the intended recipient, any disclosure, copying,
distribution
> or any action taken or omitted to be taken in reliance on it, is
prohibited
> and may be unlawful. When addressed to our clients any opinions or 
> advice contained in this email are subject to the terms and conditions 
> expressed
in
> the governing KPMG client engagement letter.
>

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



RE: Displaying is easy, capturing is not..

2003-07-30 Thread Gandle, Panchasheel
Use Map Backed Beans for that...


Panchasheel

-Original Message-
From: Alawadhi, Mona [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 30, 2003 1:32 PM
To: Struts Users Mailing List
Subject: Displaying is easy, capturing is not..


Hello Everyone,

I wonder if someone can help me with this problem. I would appreciate any
smart suggestion.

I have a JSP that displays a collection (ValueObject fields) Let's call the
collection ABC - it consists of 6 items. I might have more than one ABC
collections to display. This can be done by setting a Vector which consists
of a number of ABC collections, and simply I can iterate through the Vector
in my JSP and display all the ABC collections I have using textboxes.

When the user tries to change any of those textboxes, I should be able to
capture them. I have one submit button that I am using, and if, for example,
I have two ABC's there, I should be able to capture all 12 items. (note that
I might have 100 ABCs, in which case I have to capture 600 items.)

How can I do that using one submit button?

Thank you in advance,

Mona





*
The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorized. 

If you are not the intended recipient, any disclosure, copying, distribution
or any action taken or omitted to be taken in reliance on it, is prohibited
and may be unlawful. When addressed to our clients any opinions or advice
contained in this email are subject to the terms and conditions expressed in
the governing KPMG client engagement letter. 

*


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



RE: Displaying is easy, capturing is not..

2003-07-30 Thread Paananen, Tero
> How can I do that using one submit button?

Yes, see the discussions about indexed properties
this week. That's what they're for.

-TPP

-
This email may contain confidential and privileged material for the sole use of the 
intended recipient(s). Any review, use, retention, distribution or disclosure by 
others is strictly prohibited. If you are not the intended recipient (or authorized to 
receive for the recipient), please contact the sender by reply email and delete all 
copies of this message.  Also, email is susceptible to data corruption, interception, 
tampering, unauthorized amendment and viruses. We only send and receive emails on the 
basis that we are not liable for any such corruption, interception, tampering, 
amendment or viruses or any consequence thereof.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Displaying is easy, capturing is not..

2003-07-30 Thread atta-ur rehman
Hello Mona,

is ABC is bean that has six properties that you need to show? and then you
have a collection of ABC objects in a List or Vector? if so, you can use the
indexed properties to capture all the changes done on the page.

and yes, usually one submit button is enough for six hundred values!!!

ATTA

- Original Message - 
From: "Alawadhi, Mona" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Sent: Wednesday, July 30, 2003 10:32 AM
Subject: Displaying is easy, capturing is not..


> Hello Everyone,
>
> I wonder if someone can help me with this problem. I would appreciate any
> smart suggestion.
>
> I have a JSP that displays a collection (ValueObject fields) Let's call
the
> collection ABC - it consists of 6 items. I might have more than one ABC
> collections to display. This can be done by setting a Vector which
consists
> of a number of ABC collections, and simply I can iterate through the
Vector
> in my JSP and display all the ABC collections I have using textboxes.
>
> When the user tries to change any of those textboxes, I should be able to
> capture them. I have one submit button that I am using, and if, for
example,
> I have two ABC's there, I should be able to capture all 12 items. (note
that
> I might have 100 ABCs, in which case I have to capture 600 items.)
>
> How can I do that using one submit button?
>
> Thank you in advance,
>
> Mona
>
>
>
>
>

*
> The information in this email is confidential and may be legally
privileged.
> It is intended solely for the addressee. Access to this email by anyone
else
> is unauthorized.
>
> If you are not the intended recipient, any disclosure, copying,
distribution
> or any action taken or omitted to be taken in reliance on it, is
prohibited
> and may be unlawful. When addressed to our clients any opinions or advice
> contained in this email are subject to the terms and conditions expressed
in
> the governing KPMG client engagement letter.
>

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



Displaying is easy, capturing is not..

2003-07-30 Thread Alawadhi, Mona
Hello Everyone,

I wonder if someone can help me with this problem. I would appreciate any
smart suggestion.

I have a JSP that displays a collection (ValueObject fields) Let's call the
collection ABC - it consists of 6 items. I might have more than one ABC
collections to display. This can be done by setting a Vector which consists
of a number of ABC collections, and simply I can iterate through the Vector
in my JSP and display all the ABC collections I have using textboxes.

When the user tries to change any of those textboxes, I should be able to
capture them. I have one submit button that I am using, and if, for example,
I have two ABC's there, I should be able to capture all 12 items. (note that
I might have 100 ABCs, in which case I have to capture 600 items.)

How can I do that using one submit button?

Thank you in advance,

Mona




*
The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorized. 

If you are not the intended recipient, any disclosure, copying, distribution
or any action taken or omitted to be taken in reliance on it, is prohibited
and may be unlawful. When addressed to our clients any opinions or advice
contained in this email are subject to the terms and conditions expressed in
the governing KPMG client engagement letter. 
*


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]