How to implement dynamic response view (e.g. logout)

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

How to implement dynamic response view (e.g. logout)

Brett
We need to change the behavior of the “logout” feature in one of our
custom ofbiz applications.  We want the response view to depend on
specific session information about the user.  For example, the user's
role or other security rights the user may have.

Here is one way to do it but I wanted to know if there was a preferred
method for this type of feature.

<request-map uri="logout">
  <security https="true" auth="true"/>
  <event type="java" path="<custom_logout_event – still calls the
ofbiz logout" invoke="logout"/>
  <response name=”option1” type=”request” value=”LoginPage1”/>
  <response name="option2" type="request" value="LoginPage2"/>
  <response name="option3" type="request" value="LoginPage3"/>
  <response name="error" type="view" value="error"/>
</request-map>

In the custom_logout_event, the code would check session variable
information for the user, call the standard ofbiz logout, and then
output a response like “option1, option2, option3, or error” depending
on the session information.  The controller would then display the
correct response view defined in the controller.xml file.

Your feedback on this solution is appreciated.



Brett
Reply | Threaded
Open this post in threaded view
|

Re: How to implement dynamic response view (e.g. logout)

Ashish Vijaywargiya-5
Hello Brett,

The solution that you are proposing looks good to me.
I don't see any problem in this approach.

+1 from me on this.

--
Ashish

Brett Palmer wrote:

> We need to change the behavior of the “logout” feature in one of our
> custom ofbiz applications.  We want the response view to depend on
> specific session information about the user.  For example, the user's
> role or other security rights the user may have.
>
> Here is one way to do it but I wanted to know if there was a preferred
> method for this type of feature.
>
> <request-map uri="logout">
>   <security https="true" auth="true"/>
>   <event type="java" path="<custom_logout_event – still calls the
> ofbiz logout" invoke="logout"/>
>   <response name=”option1” type=”request” value=”LoginPage1”/>
>   <response name="option2" type="request" value="LoginPage2"/>
>   <response name="option3" type="request" value="LoginPage3"/>
>   <response name="error" type="view" value="error"/>
> </request-map>
>
> In the custom_logout_event, the code would check session variable
> information for the user, call the standard ofbiz logout, and then
> output a response like “option1, option2, option3, or error” depending
> on the session information.  The controller would then display the
> correct response view defined in the controller.xml file.
>
> Your feedback on this solution is appreciated.
>
>
>
> Brett
>  


smime.p7s (4K) Download Attachment