[
https://issues.apache.org/jira/browse/ORCHESTRA-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12548721
]
Mario Ivankovits commented on ORCHESTRA-13:
-------------------------------------------
But the RequestParameterProvidedManager should not see any url with
el-expressions in it.
The UrlParameterNavigationHandler should have replaced them all.
If this didn't work I see two possible problems:
1) UrlParameterNavigationHandler is not configured correctly (needs to be done
manually, is not setup by orchestra)
2) The UrlParameterNavigationHandler is broken :-(
> RequestParameterProviderManager fails when template URL includes EL
> expressions
> -------------------------------------------------------------------------------
>
> Key: ORCHESTRA-13
> URL: https://issues.apache.org/jira/browse/ORCHESTRA-13
> Project: MyFaces Orchestra
> Issue Type: Bug
> Components: RequestParameterProvider
> Affects Versions: 1.0
> Reporter: Simon Kitching
>
> As reported by Jonas Esser on the mailing list, a url of form
> http://foo.example?productId=#{var}
> fails badly; the final url is:
> http://foo.example?productId=&contextId=1val
> This occurs in the "petstore" orchestra example, when viewing a product's
> details.
> The problem is that RequestParameterProvidedManager thinks the "#" is a url
> fragment marker. Query params go before fragment markers, eg
> http://foo.example?productId=5#anchor
> does correctly become
> http://foo.example?productId=5&contextId=1#anchor
> But #{...} is NOT an anchor. In the petstore example, the url can be found in
> faces-config.xml:
> <navigation-case>
> <from-outcome>ProductDetails</from-outcome>
>
> <to-view-id>/mops/ProductDetail.jsp?productId=#{param.productId}</to-view-id>
> <redirect/>
> </navigation-case>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
