Hello,
My jsf page can only be accessed via URL which forwards to this JSF for
security reasons. Before doing forward server put other required stuff
into session context (as user
permissions, mode for extra/intranet viewing). Depending via which page
it got into jsf this information in the context will be different. The
only way to get to jsf page is via this
set of URLs which do internal forward. Now I've started using jsf form
h:form and h:commandLink and hit a major roadblock.
h:commandLink submits only to JSF which contains parent h:form and it
does it by direct reffering to JSF. It simply ignores current URL path.
EX: http://localhost/portal/JsfApp/form.jsf
<http://localhost/portal/JsfApp/form.jsf> is only accessible via
http://localhost/portal/externalModeCheck?app=JsfApp&page=form.jsf
<http://localhost/portal/externalModeCheck?app=JsfApp&page=form.jsf>
or
http://localhost/portal/internalModeSecurityCheck?app=JsfApp&page=form.jsf
<http://localhost/portal/internalModeSecurityCheck?app=JsfApp&page=form.jsf>
and has a form and commandLink
and commandLink submits it directly to
http://localhost/portal/JsfApp/form.jsf
<http://localhost/portal/JsfApp/form.jsf> which is not accessible
It should go via
http://localhost/portal/internalModeCheck?&app=JsfApp&page=form.jsf&additionalParams=blabla
<http://localhost/portal/internalModeCheck?&app=JsfApp&page=form.jsf&additionalParams=blabla>
or
http://localhost/portal/externalModeCheck?&app=JsfApp&page=form.jsf&additionalParams=blabla
<http://localhost/portal/externalModeCheck?&app=JsfApp&page=form.jsf&additionalParams=blabla>
depending on how I got there in first place.
One case where I need to use h:commandLink is tomahawk master/detail
dataTable.
What is the workaround for this case with myfaces?
Thanks,
--MG
