That's ridiculous.  If that were true, then just give up and go home.

--
James Mitchell
Software Engineer / Struts Evangelist
http://www.struts-atlanta.org
770-822-3359
AIM:jmitchtx




> -----Original Message-----
> From: ansuman_behera [mailto:[EMAIL PROTECTED]
> Sent: Friday, August 08, 2003 2:51 AM
> To: Struts Users Mailing List
> Subject: RE: method to get new Id to next action when old Id is in
> request?
> 
> 
> what if there is a restriction that the developers should not be 
> using hidden variables? what do you do in this case?
> 
> -----Original Message-----
> From: Rohit Aeron [mailto:[EMAIL PROTECTED]
> Sent: Friday, August 08, 2003 11:54 AM
> To: Struts Users Mailing List
> Subject: RE: method to get new Id to next action when old Id is in
> request?
> 
> 
> Try putting up id as a hidden variable...
> 
> Eg:
> 
> <html:hidden name="FormBean" property="id"/>
> 
> 
> it would work 
> 
> regards
> Rohit
> 
> -----Original Message-----
> From: Adam Hardy [mailto:[EMAIL PROTECTED] 
> Sent: Friday, August 08, 2003 2:56 AM
> To: Struts Users Mailing List
> Subject: method to get new Id to next action when old Id is in request?
> 
> I have two actions chained together. They both take the same formbean. 
> The first is sectionInsert.do and the second, which sectionInsert 
> forwards to on success, is sectionEdit.do
> 
> sectionInsert.do receives the properties of a Section in the request 
> parameters, including id=0 where it is 0 because it does not exist in 
> the DB yet. So it inserts the new Section into the DB and returns the 
> new id, which is needed by sectionEdit to put into the html for the edit 
> page.
> 
> I originally thought I could save the new id to the formbean and this 
> would get passed on, but sectionEdit instantiates its own formbean and 
> fills it with the request parameters - include id=0.
> 
> Is there an intuitive way of passing on the new id?
> 
> I already use sectionEdit.do as a first action by calling it with an id 
> on a querystring, where the formbean picks it up. I would like to use a 
> method that is easy for both these situations.
> 
> I'd appreciate any inspiration.
> Adam
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 
> *----------
> This message and any attachment(s) is intended only for the use 
> of the addressee(s) and may contain information that is 
> PRIVILEGED and CONFIDENTIAL. If you are not the intended 
> addressee(s), you are hereby notified that any use, distribution, 
> disclosure or copying of this communication is strictly 
> prohibited. If you have received this communication in error, 
> please erase all copies of the message and its attachment(s) and 
> notify the sender or Kanbay postmaster immediately.
> 
> Any views expressed in this message are those of the individual 
> sender and not of Kanbay.
> 
> Although we have taken steps to ensure that this e-mail and any 
> attachment(s) are free from any virus, we advise that in keeping 
> with good computing practice the recipient should ensure they are 
> actually virus free.
> 
> 
> ---------------------------------------------------------------------
> 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]

Reply via email to