[
https://issues.apache.org/jira/browse/OFBIZ-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621736#action_12621736
]
David E. Jones commented on OFBIZ-1915:
---------------------------------------
This is an interesting enhancement.
One strange thing about it is that the functionality is enabled with a new
response type, but then that new response type is configured through attributes
added to the "response" element itself, even though that are not used for
anything else.
I'm not sure what the best solution is to this issue, but we should at least
document these attributes well so that people know that they don't apply to
other response types (even though it might make sense for them to...).
-David
> Improving request redirects
> ---------------------------
>
> Key: OFBIZ-1915
> URL: https://issues.apache.org/jira/browse/OFBIZ-1915
> Project: OFBiz
> Issue Type: Improvement
> Components: framework
> Affects Versions: SVN trunk
> Reporter: Wickersheimer Jeremy
> Assignee: Si Chen
> Priority: Minor
> Fix For: SVN trunk
>
> Attachments: redirect.patch
>
>
> There are some issues with request-redirect and request-redirect-noparam, the
> former does not work very well with service multi and most of the time we do
> not need all the parameters to be in the redirected query, the later is a bit
> too radical.
> This is something that i have been thinking for a while when running into
> these two kind of issues:
> - when i want to redirect to a viewXXX page, i just want to have the XXXId
> in my redirect
> - after i create an entity i want to redirect to the viewXXX page with the
> XXXId visible in the query
> This patch i how we dealt with those in Opentaps, so maybe you are interested
> in applying to Ofbiz as well.
> The end result is nicer and more user friendly redirects.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
