This is a common problem.. you should look at the Shale Dialog
Manager: http://shale.apache.org/features-dialog-manager.html, it
tries to address this very exact problems.
Cosma
2006/8/1, [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
Thank you all for your responses. It's been a great help and v
Thank you all for your responses. It's been a great help and very
interesting reading.
We have a shared jsp page; there are three paths to it. Navigation has to
return to
the jsp that took the user to this particular page.
So we set a 'context' variable in session and wanted to use this fo
> You can always write an action method, and return different outcomes,
> if you want to reuse the view.
>
Yes, but different outcomes go to different VIEWS not to different
actions. So what you're doing then is to reuse the action, not the view!
What if I want one particular view to call differe
You can always write an action method, and return different outcomes,
if you want to reuse the view.
Cosma
2006/8/1, Matthias Fischer <[EMAIL PROTECTED]>:
Hm, that's right. what I had in mind when I answered Tom's question was
that session.foo contains an action binding string. But then you wo
Hm, that's right. what I had in mind when I answered Tom's question was
that session.foo contains an action binding string. But then you would
have to call
#{${session.foo}} - if that works at all.
If that is what Tom intended it does make sense to me:
A button that leads to a different action de
It may work... can I ask why you are designing things this way? It
seems a bit odd to me to add another level of abstraction on page
navigation: an expression that resolve to a string that is matched
against navigation rules that finally defines a view (!)
Cosma
2006/7/31, Matthias Fischer <[EMA
> I think that the problem is that, if EL is found in the action
> attribute, JSF tries to use it as an action method (it attemps to
> "call" it)..
That's what I suppose. So JSTL EL should solve it as we have no method
bindings here...
I think that the problem is that, if EL is found in the action
attribute, JSF tries to use it as an action method (it attemps to
"call" it)..
2006/7/31, Matthias Fischer <[EMAIL PROTECTED]>:
> I wanted to create a command button like
Hi,
I have not tried that yet, neither do I know why it sh
> I wanted to create a command button like
Hi,
I have not tried that yet, neither do I know why it should not work. But
I think the JSTL EL could solve this problem.
Try to use ${session.foo} instead and let me know whether it works, please.
Kind regards
Matthias
.foo}
#{paramValues.foo[2]}
#{requestScope.foo.bar}
#{view.locale}
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 27, 2006 1:38 PM
To: MyFaces Discussion
Subject: RE: is there a way to pull a session scope variable directly
into a jsf tag?
Thank you James
: James Reynolds [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 27, 2006 2:41 PM
To: MyFaces Discussion
Subject: RE: is there a way to pull a session scope variable directly into
a
jsf tag?
There are some implicit variables to simplify accessesing objects in
session
or application scope...
#{sess
pull a session scope variable directly into a
jsf tag?
There are some implicit variables to simplify accessesing objects in session
or application scope...
#{sessionScope.foo.bar}
Or
#{applicationScope.foo.bar}
I haven't tried this for navigation as you've described, but it works
There are some implicit variables to simplify accessesing objects in
session or application scope...
#{sessionScope.foo.bar}
Or
#{applicationScope.foo.bar}
I haven't tried this for navigation as you've described, but it works
great for tying object properties to controls.
JR
-Original
13 matches
Mail list logo
