myfaces-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Delbecq <>
Subject Re: Intercepting the request
Date Thu, 20 Sep 2007 20:34:42 GMT
If the problem is only that you do not want to display the log field at 
same time, you can put the log field entry in a section that is only 
"rendered" after data are validated. It's still the same "view" but user 
now only see the log fields.

Another possibility,  with one page for each data set but only one log page

page1: fill  data change
page 1 action : store in session bean a "request for change objet" (can 
even be your action bean itself :p)
navigate to logEntry
logEntry: fill log informaton
logEntry action: store log informations, execute the "request for 
change" object you stored

If you want to intercept various steps of JSF lifecycle, this can be 
done with a phase listener. However,while phase listener can be great as 
a monitoring tool or to handle special query parameter as initialisation 
stuff for beans, it can become a mess if you use it to delay actions.

Sushma Sharma a écrit :
> My pages are already really big, so I do not want to add audit fields 
> also in the same page.  I have one page where I have included audit 
> fields also and I am being asked to do it the other way. So, I wanted 
> to find a standard way to capture the audit info as I am going to need 
> it for other pages also.
> */David Delbecq <>/* wrote:
>     Why don't you put the 'audit log' fields in page1, along with
>     datas they
>     change. It's not mandatory, in JSF, that the same bean be used for
>     all
>     component in form. You can update and gather datas from various
>     beans /
>     various request scope in a single form. That way you do all in a
>     single
>     move.
>     Sushma Sharma a écrit :
>     > Hi,
>     >
>     > I have many jsf pages(page1, page2, page 3, page4) where users can
>     > make changes, but before they can submit/save the changes, I
>     have to
>     > take them to audit log page, where they have to enter the remedy id
>     > and description of the changes. Currently what I am doing is I am
>     > several pages(auditpage1, auditpage2, auditpage3 etc..) for the
>     audit
>     > log and from each page(page1) I take the users to corresponding
>     audit
>     > page(auditpage1) and in this audt page I specify the actual bean
>     > action to save the changes.
>     > Is it possible that I specify actual action methods in page1and on
>     > clicking the commandButton/link, I intercept the request and
>     take then
>     > to a single audit log and after user enters the details and clicks
>     > another button, resume the action clicked on the page1.
>     > let me know if it is possible and how to do it? If there is any
>     other
>     > better way to do it, please suggest.
>     > Thanks,
>     >
>     >
>     > The word "Impossible" itself says " I m possible".
>     > */Sushma/**//*
>     >
>     >
>     ------------------------------------------------------------------------
>     > Be a better Heartthrob. Get better relationship answers
>     > from
>     > someone who knows.
>     > Yahoo! Answers - Check it out.
> The word "Impossible" itself says " I m possible".
> */Sushma/**//*
> ------------------------------------------------------------------------
> Got a little couch potato?
> Check out fun summer activities for kids. 
> <*>

View raw message