Sorry, I meant: Costa Basil <[EMAIL PROTECTED]> wrote: page: faces-config.xml: goViewObject
viewObject.jsp?test=#{param.test}&foo=#{param.foo} It will redirect you to:viewObject.jsp?test=testValue&foo=fooValuePlease note I used the prefix url handli
page: faces-config.xml: goViewObject viewObject.jsp?test=#{param.test}&foo=#{param.foo} It will redirect you to:viewObject.jsp?test=testValue&foo=fooValuePlease note I used the prefix url handling.Matthias Wessendorf <[EMAIL PROTECTED]> wrote: looks interesting,
looks interesting, what happens, if you have to EL based params ?
like
viewObject.jsp?test=#{param.test}&foo=#{param.foo}
.Matthias
On Wed, 2006-02-15 at 16:32 -0500, Costa Basil wrote:
> One thing though, the implementation below blows up for normal view
> ids so I replaced it with the follow
One thing though, the implementation below blows up for normal view ids so I replaced it with the following code:String targetViewId = navigationCase.getToViewId();if (targetViewId.indexOf("#{") != -1){ ValueBinding vb = facesContext.getApplication().createValueBinding(navigationCase.getToViewId()
Hi,This is a solution to an issue that some people complained about and that is how to preserve request objects or other objects when you do a redirect.It is actually possible to specify JSF EL expressions in the to-view-id view. Example:In faces-config.xml I have: goViewObject viewObject.jsp?tes
5 matches
Mail list logo
