Thanks for your answer.

I don't know what's happening with my thread but I can't see your answer on
nabble. Not a problem, I can see it in an other way.

But your answer doesn't explain me why the attribute is lost between two
struts actions, or I don't understand.
The real problem is that an attribute, contained in the context, exists in a
first stuts action, and not in a second one. And the two actions are the one
after the other, like in my example:
http://www.nabble.com/context-value-to19593451.html

I hope I am clear.

Thanks in advance.




mgainty wrote:
> 
> 
> access it with straight web.xml context-param 
> <context-param>
>    <param-name>qualifying_requirements</param-name>
>    <param-value>poor_english</param-value>
> </context-param> 
>  
> //you can then access it via
> getServletContext().getInitParameter("qualifying_requirements");Is there
> something specific you needed?
> Martin 
> ______________________________________________ 
> Disclaimer and confidentiality note 
> Everything in this e-mail and any attachments relates to the official
> business of Sender. This transmission is of a confidential nature and
> Sender does not endorse distribution to any party other than intended
> recipient. Sender does not necessarily endorse content contained within
> this transmission. 
> 
> 
>> Date: Sun, 21 Sep 2008 04:07:53 -0700
>> From: [EMAIL PROTECTED]
>> To: user@struts.apache.org
>> Subject: context value
>> 
>> 
>> Hello, sorry for my bad english.
>> 
>> Does someone knows why a context value could be lost between two struts
>> actions?
>> 
>> 
>> For an example,
>> In SecondAction:
>> req.getSession(true).getServletContext().getAttribute("key")) returns
>> "value",
>> In ThirdAction:
>> req.getSession(true).getServletContext().getAttribute("key")) returns
>> null
>> 
>> with the following struts actions:
>> 
>>         <action 
>>             path="/secondAction" 
>>             name="secondAction" 
>>             type="appli.struts.actions.SecondAction"
>>         >
>>             <forward name="valid" path="/thirdAction.do"/>
>>             <forward name="invalid" path="/error.jsp" />
>>         </action>
>>         
>>         <action 
>>             path="/thirdAction" 
>>             name="thirdAction" 
>>             type="appli.struts.actions.ThirdAction"
>>         >
>>             <forward name="valid" path="/result2.jsp" />
>>             <forward name="invalid" path="/error.jsp" />
>>         </action>
>> 
>> 
>> 
>> I haven't this problem when I do this at home, with a simple
>> configuration.
>> But is there something that could explain that I have this problem at
>> work
>> in your advice? Configuration parameters, the scope of the context,
>> etc... ?
>> 
>> 
>> Thank you in advance.
>> -- 
>> View this message in context:
>> http://www.nabble.com/context-value-tp19593451p19593451.html
>> Sent from the Struts - User mailing list archive at Nabble.com.
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>> 
> 
> _________________________________________________________________
> Stay up to date on your PC, the Web, and your mobile phone with Windows
> Live.
> http://clk.atdmt.com/MRT/go/msnnkwxp1020093185mrt/direct/01/
> 

-- 
View this message in context: 
http://www.nabble.com/context-value-tp19593451p19613111.html
Sent from the Struts - User mailing list archive at Nabble.com.


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

Reply via email to