Re: Request: Property vs Attribute

2002-02-16 Thread Andreas Mack
On Fri, 2002-02-15 at 14:04, Ted Husted wrote: You might want to start with an ActionForm bean that represents the OK dialog page. This should include properties for a base forward and for a paramId and param (like the html:link tag). The Action for the OK button would then look for

Re: Request: Property vs Attribute

2002-02-15 Thread Keith
Users Mailing List Subject: Re: Request: Property vs Attribute You might try adding the userId property to the ActionForm, and seeing if that approach works better for you. -- Ted Husted, Husted dot Com, Fairport NY USA. -- Java Web Development with Struts. -- Tel +1 585 737-3463

Re: Request: Property vs Attribute

2002-02-15 Thread Andreas Mack
On Fri, 2002-02-15 at 02:19, Ted Husted wrote: I have a question along these lines: Quite often I have thing like an acknowledge page, very much like an Ok Dialog: The password has been changed successfully. html:submitOK/html:submit. I'm toying with the idea of generalize this by having an

Generic Dialog/Coupled Pages(Was: Request: Property vs Attribute)

2002-02-15 Thread Keith
For more details some code search the archive at http://www.mail-archive.com/struts-user%40jakarta.apache.org/ for:- chainToPage - something I wrote mean to refine one day. No tags - controlled from inside the action class. It works fine for me. It's designed for swapping between lists of data

Confirm Style (was: Request: Property vs Attribute)

2002-02-15 Thread Keith
maybe heading off topic - forgive me - but I want struts systems to be well designed! The web is so darn slow - for repetitive use system confirmation/dialogs are a real pain. I'm not a designer but I feel it's best to take the user to a useful page put your message at the top of it. eg. in

Re: Request: Property vs Attribute

2002-02-15 Thread Ted Husted
You might want to start with an ActionForm bean that represents the OK dialog page. This should include properties for a base forward and for a paramId and param (like the html:link tag). The Action for the OK button would then look for the given forward, ActionForward baseForward =

Re: Confirm Style (was: Request: Property vs Attribute)

2002-02-15 Thread Andreas Mack
On Fri, 2002-02-15 at 12:45, Keith wrote: maybe heading off topic - forgive me - but I want struts systems to be well designed! The web is so darn slow - for repetitive use system confirmation/dialogs are a real pain. I'm not a designer but I feel it's best to take the user to a useful

RE: Confirm Style (was: Request: Property vs Attribute)

2002-02-15 Thread Emaho, Ghoot
(was: Request: Property vs Attribute) maybe heading off topic - forgive me - but I want struts systems to be well designed! The web is so darn slow - for repetitive use system confirmation/dialogs are a real pain. I'm not a designer but I feel it's best to take the user to a useful

Request: Property vs Attribute

2002-02-14 Thread Jakkampudi, ChandraseKhar
I have a jsp that displays details of a user. The display is in a form that can also be used to modify user details. Access to this page is via a url like http://xyz.com/userDetails.do?userID=123. However the userid is not a editable field and I use a hidden variable to pass this information back

RE: Request: Property vs Attribute

2002-02-14 Thread Jakkampudi, ChandraseKhar
]] Sent: Thursday, February 14, 2002 2:29 PM To: 'Struts Users Mailing List' Subject: Request: Property vs Attribute I have a jsp that displays details of a user. The display is in a form that can also be used to modify user details. Access to this page is via a url like http://xyz.com/userDetails.do

RE: Request: Property vs Attribute

2002-02-14 Thread Pedone, Tim
. Tim -Original Message- From: Jakkampudi, ChandraseKhar [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 14, 2002 12:29 PM To: 'Struts Users Mailing List' Subject: Request: Property vs Attribute I have a jsp that displays details of a user. The display is in a form that can also be used

RE: Request: Property vs Attribute

2002-02-14 Thread Jakkampudi, ChandraseKhar
: Pedone, Tim [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 14, 2002 3:44 PM To: 'Struts Users Mailing List' Subject: RE: Request: Property vs Attribute Is userID a member of your ActionForm subclass? If you make it a member of your ActionForm, it will get maintained (provided you don't wipe

Re: Request: Property vs Attribute

2002-02-14 Thread Ted Husted
' Subject: RE: Request: Property vs Attribute Is userID a member of your ActionForm subclass? If you make it a member of your ActionForm, it will get maintained (provided you don't wipe it out in your reset() method) for you if you have a html:hidden property=userID/ tag in your jsp. I tried

RE: Request: Property vs Attribute

2002-02-14 Thread Jakkampudi, ChandraseKhar
place. Is this not the right way to do things? Any help is appreciated. -JC -Original Message- From: Ted Husted [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 14, 2002 4:03 PM To: Struts Users Mailing List Subject: Re: Request: Property vs Attribute As long

Re: Request: Property vs Attribute

2002-02-14 Thread Ted Husted
in the first place. Is this not the right way to do things? Any help is appreciated. -JC -Original Message- From: Ted Husted [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 14, 2002 4:03 PM To: Struts Users Mailing List Subject: Re: Request: Property vs Attribute As long

RE: Request: Property vs Attribute

2002-02-14 Thread Jakkampudi, ChandraseKhar
- From: Ted Husted [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 14, 2002 5:46 PM To: Struts Users Mailing List Subject: Re: Request: Property vs Attribute You might try adding the userId property to the ActionForm, and seeing if that approach works better for you. -- Ted Husted, Husted