> I also set the top.vm property to be top_default.jsp in which 
> i declare a session bean called "systemBean".

IMOHO, I would avoid storing or creating anything persistent in your view
layer (your JSP).  I would create a custom SessionValidator (see
org.apache.jetspeed.modules.actions.JetspeedSessionValidator) to set this
value for you as it will be called prior to executing actions/templates.

Hth,
*================================* 
| Scott T Weaver                 |
| <[EMAIL PROTECTED]>            | 
| Apache Jetspeed Portal Project |
| Apache Pluto Portlet Container |
*================================*

> -----Original Message-----
> From: Archana Turaga [mailto:[EMAIL PROTECTED] 
> Sent: Thursday, December 18, 2003 5:45 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Accessing session beans in a Login action class
> 
> 
> Well as i'm a newbie to the JSP technology as well as to 
> jetspeed i sort of messed up in my implementation. 
> 
> I was not using the correct method to instantiate beans. I 
> corrected that and everything worked.
> 
> Although i would appreciate any input on my method of 
> overriding the JLoginUser class. Is that the recommended way?
> 
> >>> [EMAIL PROTECTED] 12/17/03 08:09PM >>>
> Hi,
> I had a question as a newbie user of jetspeed.
> 
> I have my own login action class called CCLoginUser.java. 
> This class is the same as the JLoginUser except i need to 
> some custom stuff related to our rmi server.
> 
> I also set the top.vm property to be top_default.jsp in which 
> i declare a session bean called "systemBean".
> 
> When i try to get an instance of this bean in the 
> CCLoginUser.java using the following command: SystemBean 
> sBean = (SystemBean) 
> rundata.getRequest().getSession().getAttribute ("systemBean");
> 
> I get the sBean object as null..
> What is really wrong here.
> 
> Thanks and i await your reply,
> Regards,
> Archana
> 

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

Reply via email to