Thanks Rahul, and sorry for the double address. I'm using A4J and the action is posted from an AJAX Button. I would like to use Shale for configure the real Action Method to execute but I don't know if there is some problem if Shale build the view in response. On the documentation of A4J there is following sentence:
"****************** action method must return null if you want to have an Ajax Response with a partual page update. This is regular mode called "Ajax request generates Ajax Response". In case of action does not return null, but the action outcome that matches one of navigation rules, RichFaces starts to work in "Ajax request generates Non-Ajax Response" mode. This mode might be helpful in two major cases: - RichFaces allows to organize a page flow inside the a4j:include component. This is a typical scenario for Wizard like behavior. The new content is rendered inside the a4j:include area. The content is taken from the navigation rule of the faces configuration file (usually, the faces-config.xml). Note, that the content of the "wizard" is not isolated from the rest of the page. The included page should not have own f:view (it does not matter if you use facelets). You need to have an Ajax component inside the a4j:include to navigate between the wizard pages. Otherwize, the whole page update will be performed. - If you want to involve the server side validators and navigate to the next page only if the Validation phase is passed successfully, you can replace h:commandButton with a4j:commandButton and point to the action method that navigates to the next page. If Validation process fails, the partial page update will occur and a user will see an error message. Otherwize, the application proceeds to the next page. Make sure, you define <redirect /> option for the navigation rule to avoid memory leaks. "********** They are talking about memory leak....Do you have some idea of what they are talking about? Regards Mario -----Original Message----- From: Rahul Akolkar [mailto:[EMAIL PROTECTED] Sent: 30 gennaio 2008 23.36 To: user@shale.apache.org Subject: Re: Problem with navigation handler Please post to either dev or user list as appropriate, rather than both. I chose to continue on the user list for this query. On 1/30/08, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Hi, I'm using basic navigation handler with this configuration: > > <action name="actionRicerca" > method="#{test_stateless$ricercaSinistro.findClaim}"> > > <transition outcome="OK" target="ricercaPage" /> > > <transition outcome="error" target="Exit"/> > > </action> > > > > <view name="ricercaPage" viewId="/test_stateless/ricercaSinistro.jsp"> > > <transition outcome="ricerca" target="actionRicerca"/> > > </view> > > > > The button of my form call the action "ricerca" because I want specify > the action to call in the configuration file of dialog. > > If the action ="#{test_stateless$ricercaSinistro.findClaim}" return null > I have a loop because the control remain to the view "ricercaPage" and > call again the outcome "ricerca". > <snip/> Generally speaking, the logical outcome from an action state should not be null (try to catch, and model, those conditions that generate a null response as a separate -- or overlapping, as the case may be -- arc in your dialog / flow). -Rahul > > > Is there any one can help me? > > > > Thanks in advance > > Mario > This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.
