You must specify the attribute value for you action mapping

David Bolsover wrote:

Are you explicitly putting wigadminwizardform into session scope in OMInterfaceInfoAction?

db



-----Original Message-----
From: Chetan Sahasrabudhe [mailto:[EMAIL PROTECTED]
Sent: 26 February 2003 07:51
To: Struts Users Mailing List
Subject: Re: [Q] BEAN SCOPE


man i have attached my struts-config.xml in my privious mails check the attachment

Chetan
----- Original Message -----
From: "du Plessis, Corneil C" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Sent: Wednesday, February 26, 2003 1:13 PM
Subject: RE: [Q] BEAN SCOPE




What does you struts-config look like? The form bean and action mapping
entries.

-----Original Message-----
From: Chetan Sahasrabudhe [mailto:[EMAIL PROTECTED]
Sent: 26 February, 2003 09:34
To: Struts Users Mailing List
Subject: Re: [Q] BEAN SCOPE


OH yeh ... they r all in same webapps folder and are having refferences in same WEB-INF web.xml and struts-config.xml files.

Any changes required in my struts-config ?


btw, how is world cup going at ur end :) .... r u planning to watch India-England match :)

----- Original Message -----
From: "du Plessis, Corneil C" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Sent: Wednesday, February 26, 2003 12:50 PM
Subject: RE: [Q] BEAN SCOPE




It may be a silly question but are these actions in the same web
application?

-----Original Message-----
From: Chetan Sahasrabudhe [mailto:[EMAIL PROTECTED]
Sent: 26 February, 2003 08:47
To: Struts Users Mailing List
Subject: Re: [Q] BEAN SCOPE


Yep, I have session scope in both action mappings I have attached my struts-config along with this mail.

btw in my jsp i have form bean saying

JSP 1
<html:form action="/ominterfaceinfo.do" focus="sOMName" onsubmit="return
validateWIGAdminWizardForm(this);">

JSP 2
<html:form action="/translator.do" onsubmit="return
validateWIGAdminWizardForm(this);">


now, when I call jsp1 the bean is getting created but when I move to jsp 2 , again new bean is created.

And thatz the problem area.

Thanks
Chetan
----- Original Message -----
From: "du Plessis, Corneil C" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Sent: Wednesday, February 26, 2003 12:05 PM
Subject: RE: [Q] BEAN SCOPE




Did you put scope=session on both action mappings?

-----Original Message-----
From: Chetan Sahasrabudhe [mailto:[EMAIL PROTECTED]
Sent: 26 February, 2003 08:31
To: Struts Users Mailing List
Subject: [Q] BEAN SCOPE


Hi,
I am trying to figure out what can be the problem in my


struts-config


from yday,
will anyone tell me what can be the problem if, I am putting


scope="session"


in my action-mapping
and trying to access same formbean from two different actions.

Once the bean is created, it should be there for the session, and when


I


move to next jsp and call another action it should use same bean


rather


than


creating a new one.

I know itz creating new bean, coz I have put default constructor in my
formbean and am printing System.out.printing() through constructor.


Regards Chetan _______________________________ | | The trouble with being punctual | is that nobody's there to appreciate it. | | |_______________________________





______________________________________________

Disclaimer and confidentiality note


Everything in this e-mail and any attachments relating to the official


business of


Standard Bank Group Limited is proprietary to the company. It is


confidential, legally


privileged and protected by law. Standard Bank does not own and


endorse


any other content.


Views and opinions are those of the sender unless clearly stated as


being


that of Standard Bank.


The person addressed in the e-mail is the sole authorised recipient.


Please notify the sender


immediately if it has unintentionally reached you and do not read,


disclose or use the content


in any way.

Standard Bank can not assure that the integrity of this communication


has


been maintained nor


that it is free of errors, virus, interception or interference.

______________________________________________



______________________________________________

Disclaimer and confidentiality note


Everything in this e-mail and any attachments relating to the official


business of


Standard Bank Group Limited is proprietary to the company. It is


confidential, legally


privileged and protected by law. Standard Bank does not own and endorse


any other content.


Views and opinions are those of the sender unless clearly stated as


being


that of Standard Bank.


The person addressed in the e-mail is the sole authorised recipient.


Please notify the sender


immediately if it has unintentionally reached you and do not read,


disclose or use the content


in any way.

Standard Bank can not assure that the integrity of this communication


has


been maintained nor


that it is free of errors, virus, interception or interference.

______________________________________________

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

______________________________________________

Disclaimer and confidentiality note


Everything in this e-mail and any attachments relating to the official


business of


Standard Bank Group Limited is proprietary to the company. It is


confidential, legally


privileged and protected by law. Standard Bank does not own and endorse


any other content.


Views and opinions are those of the sender unless clearly stated as being


that of Standard Bank.


The person addressed in the e-mail is the sole authorised recipient.


Please notify the sender


immediately if it has unintentionally reached you and do not read,


disclose or use the content


in any way.

Standard Bank can not assure that the integrity of this communication has


been maintained nor


that it is free of errors, virus, interception or interference.

______________________________________________

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