In the next release, there will be *Aware interfaces for the portlet objects.
Nils-H
On 9/13/07, tom tom [EMAIL PROTECTED] wrote:
Yes in theory you are correct, but in side a S2
portlet (which implements ServletRequestAware
interface) if you try to get a handler for
HttpServletRequest
Thats sounds good, also try to have model-driven
interfaces to have the session scope Action forms in
the next release,
that also not working currently.
Also in the s:url the action tag does not evaluate
expressions, e.g if you want to have a dynamic action
name.
Pls try to address that as
On Tuesday 11 September 2007 23:03, Nils-Helge Garli wrote:
You could, but I would recommend using the *Aware interfaces in your
actions. It makes them easier to test.
Hmm.. I've always handled session data by creating an application base action
that implements a getUserData() and a
Hi,
If you are developing portlets with struts2
I doubt *Aware interfaces work properly, you have to
do it differently.
For example How we get a handler for Http request or
session is not via *Aware interfaces for portlets.
--- j alex [EMAIL PROTECTED] wrote:
Hi,
In the Struts 2 docs, it's
Hmm.. I've always handled session data by creating an application base action
that implements a getUserData() and a setUserData() method. All my actions
extend this base action. I then use an interceptor to grab the session data
build whatever object I decide to use to hold the data and
Yes in theory you are correct, but in side a S2
portlet (which implements ServletRequestAware
interface) if you try to get a handler for
HttpServletRequest object via the setServletRequest
method it basically gives null.
How we make a handler for the HttpServletRequest
object is as follows,
Hi,
In the Struts 2 docs, it's recommended to implement SessionAware for
accessing session within Action, but looking at some Webwork documentation,
http://wiki.opensymphony.com/display/WW1/SessionAware+Actions - it seems to
convey the opposite message .
Please clarify :
1. Why accessing via
Basically, for Actions you should use SessionAware (since you don't
have access to the ActionContext from within a standard Action). But
if you are writing an Interceptor, you would use ActionContext to get
access to the Session data.
(*Chris*)
On 9/11/07, j alex [EMAIL PROTECTED] wrote:
Hi,
I can do Map attibutes = ActionContext.getContext().getSession(); from an
Action - right?
On 9/11/07, Chris Pratt [EMAIL PROTECTED] wrote:
Basically, for Actions you should use SessionAware (since you don't
have access to the ActionContext from within a standard Action). But
if you are
You could, but I would recommend using the *Aware interfaces in your
actions. It makes them easier to test.
Nils-H
On 9/11/07, j alex [EMAIL PROTECTED] wrote:
I can do Map attibutes = ActionContext.getContext().getSession(); from an
Action - right?
On 9/11/07, Chris Pratt [EMAIL PROTECTED]
On 9/11/07, j alex [EMAIL PROTECTED] wrote:
I can do Map attibutes = ActionContext.getContext().getSession(); from an
Action - right?
Wow, I guess you can. I've never ever needed to access the
ActionContext from an Action, so I never even noticed it was possible.
Pretty sure I'll stick with
11 matches
Mail list logo
