Problem with navigation handler
|
View:
New views
13 Messages
—
Rating Filter:
Alert me
|
 |
Problem with navigation handler
by mario.buonopane
::
Rate this Message:
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". 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. |
|
|
Re: Problem with navigation handler
by Rahul Akolkar
::
Rate this Message:
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, mario.buonopane@... <mario.buonopane@...> 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". > 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 > |
|
|
RE: Problem with navigation handler
by mario.buonopane
::
Rate this Message:
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:rahul.akolkar@...] Sent: 30 gennaio 2008 23.36 To: user@... 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, mario.buonopane@... <mario.buonopane@...> 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 > 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. |
|
|
Re: Problem with navigation handler
by samju
::
Rate this Message:
Your aim is to apply a ajax call on ricercaSinistro.jsp.
If i got what you means, I think you may do the follow: The outcome of the Ajax-Call-action can (should )return null. This Ajax action should be handle outside the Dialog Configuration File. (we can mix dialog and non dialog action). The Pre-Action-State should have as target the dialog End-State. <action name="actionRicerca" method="#{ test_stateless$ricercaSinistro.findClaim }"> <transition outcome="OK" target="Exit" /> </action> <view name="ricercaPage" viewId="/test_stateless/ricercaSinistro.jsp "> In this View State we can call an Ajax action with the needed null outcome. <transition outcome=" exitdialogaction" target=" exitdialog " /> </view> <end name=exit viewId="/test_stateless/ricercaSinistro.jsp”> <end name=exitdialog viewId="/test_stateless/home.jsp”> I hope this will help
|
|
|
RE: Problem with navigation handler
by mario.buonopane
::
Rate this Message:
I'm sorry, but I don't understand....
If I return null from the action, how can Shale go do transition "OK" ? -----Original Message----- From: samju [mailto:julsamusa@...] Sent: 2 febbraio 2008 12.25 To: user@... Subject: Re: Problem with navigation handler Your aim is to apply a ajax call on ricercaSinistro.jsp. If i got what you means, I think you may do the follow: The outcome of the Ajax-Call-action can (should )return null. This Ajax action should be handle outside the Dialog Configuration File. (we can mix dialog and non dialog action). The Pre-Action-State should have as target the dialog End-State. <action name="actionRicerca" method="#{ test_stateless$ricercaSinistro.findClaim }"> <transition outcome="OK" target="Exit" /> </action> <view name="ricercaPage" viewId="/test_stateless/ricercaSinistro.jsp "> In this View State we can call an Ajax action with the needed null outcome. <transition outcome=" exitdialogaction" target=" exitdialog " /> </view> <end name=exit viewId="/test_stateless/ricercaSinistro.jsp"> <end name=exitdialog viewId="/test_stateless/home.jsp"> I hope this will help mario.buonopane 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". > > > > 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 > received it in error, please notify the sender immediately and delete the > original. Any other use of the email by you is prohibited. > > -- View this message in context: http://www.nabble.com/Problem-with-navigation-handler-tp15180522p1524192 6.html Sent from the Shale - User mailing list archive at Nabble.com. 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. |
|
|
RE: Problem with navigation handler
by samju
::
Rate this Message:
1- findClaim() do return the Transition "OK"
2- for your ajax call we do not have to use dialog conf. stuff. work outside the Dialog so return null from non-Dialog action! public String nonDialogAction(){ prepare the ajax call /*as you mentioned befor the output schould be null*/ return null; /* will let us refresh the last Dialog-State-View. This View is the Transition outcome "OK" from a dialog-Action*/ } public String dialogAction(){ .....do smth.. return OK; } Sam
|
|
|
RE: Problem with navigation handler
by mario.buonopane
::
Rate this Message:
So, in the JSP I call directly the action, for example in my button:
#{test_stateless$ricercaSinistro.nonDialogAction } Mario -----Original Message----- From: samju [mailto:julsamusa@...] Sent: 4 febbraio 2008 14.27 To: user@... Subject: RE: Problem with navigation handler 1- findClaim() do return the Transition "OK" 2- for your ajax call we do not have to use dialog conf. stuff. work outside the Dialog so return null from non-Dialog action! public String nonDialogAction(){ prepare the ajax call /*as you mentioned befor the output schould be null*/ return null; /* will let us refresh the last Dialog-State-View. This View is the Transition outcome "OK" from a dialog-Action*/ } public String dialogAction(){ .....do smth.. return OK; } Sam mario.buonopane wrote: > > I'm sorry, but I don't understand.... > If I return null from the action, how can Shale go do transition "OK" ? > > > > > -----Original Message----- > From: samju [mailto:julsamusa@...] > Sent: 2 febbraio 2008 12.25 > To: user@... > Subject: Re: Problem with navigation handler > > > Your aim is to apply a ajax call on ricercaSinistro.jsp. > If i got what you means, I think you may do the follow: > > The outcome of the Ajax-Call-action can (should )return null. > This Ajax action should be handle outside the Dialog Configuration > (we > can mix dialog and non dialog action). > > The Pre-Action-State should have as target the dialog End-State. > > <action name="actionRicerca" > method="#{ test_stateless$ricercaSinistro.findClaim }"> > <transition outcome="OK" target="Exit" /> > </action> > > <view name="ricercaPage" viewId="/test_stateless/ricercaSinistro.jsp > In this View State we can call an Ajax action with the needed null > outcome. > <transition outcome=" exitdialogaction" target=" exitdialog " /> > > </view> > <end name=exit viewId="/test_stateless/ricercaSinistro.jsp"> > <end name=exitdialog viewId="/test_stateless/home.jsp"> > > I hope this will help > > > mario.buonopane 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" >> >> <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". >> >> >> >> 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. >> >> > > -- > View this message in context: > > 6.html > Sent from the Shale - User mailing list archive at Nabble.com. > > > > > 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. > > -- View this message in context: http://www.nabble.com/Problem-with-navigation-handler-tp15180522p1526807 0.html Sent from the Shale - User mailing list archive at Nabble.com. 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. |
|
|
RE: Problem with navigation handler
by samju
::
Rate this Message:
any progress mario?
Sam
|
|
|
RE: Problem with navigation handler
by mario.buonopane
::
Rate this Message:
Yes Sam, I decided that for all AJAX Actions I don't use Dialog Manager
features but in the page I call directly the action, for example in my button: #{test_stateless$ricercaSinistro.nonDialogAction } and the action return null. What do you think? Thanks, Mario -----Original Message----- From: samju [mailto:julsamusa@...] Sent: 7 febbraio 2008 16.01 To: user@... Subject: RE: Problem with navigation handler any progress mario? Sam mario.buonopane wrote: > > So, in the JSP I call directly the action, for example in my button: > #{test_stateless$ricercaSinistro.nonDialogAction } > > Mario > > -----Original Message----- > From: samju [mailto:julsamusa@...] > Sent: 4 febbraio 2008 14.27 > To: user@... > Subject: RE: Problem with navigation handler > > > 1- findClaim() do return the Transition "OK" > 2- for your ajax call we do not have to use dialog conf. stuff. work > outside > the Dialog > so return null from non-Dialog action! > > public String nonDialogAction(){ > > prepare the ajax call > /*as you mentioned befor the output schould be null*/ > > return null; > /* will let us refresh the last Dialog-State-View. This View is the > Transition outcome "OK" from a dialog-Action*/ > } > > public String dialogAction(){ > .....do smth.. > return OK; > } > > Sam > > > mario.buonopane wrote: >> >> I'm sorry, but I don't understand.... >> If I return null from the action, how can Shale go do transition "OK" > ? >> >> >> >> >> -----Original Message----- >> From: samju [mailto:julsamusa@...] >> Sent: 2 febbraio 2008 12.25 >> To: user@... >> Subject: Re: Problem with navigation handler >> >> >> Your aim is to apply a ajax call on ricercaSinistro.jsp. >> If i got what you means, I think you may do the follow: >> >> The outcome of the Ajax-Call-action can (should )return null. >> This Ajax action should be handle outside the Dialog Configuration > File. >> (we >> can mix dialog and non dialog action). >> >> The Pre-Action-State should have as target the dialog End-State. >> >> <action name="actionRicerca" >> method="#{ test_stateless$ricercaSinistro.findClaim }"> >> <transition outcome="OK" target="Exit" /> >> </action> >> >> <view name="ricercaPage" viewId="/test_stateless/ricercaSinistro.jsp > "> >> In this View State we can call an Ajax action with the needed null >> outcome. >> <transition outcome=" exitdialogaction" target=" exitdialog " /> >> >> </view> >> <end name=exit viewId="/test_stateless/ricercaSinistro.jsp"> >> <end name=exitdialog viewId="/test_stateless/home.jsp"> >> >> I hope this will help >> >> >> mario.buonopane 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". >>> >>> >>> >>> 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 >> the >>> original. Any other use of the email by you is prohibited. >>> >>> >> >> -- >> View this message in context: >> > http://www.nabble.com/Problem-with-navigation-handler-tp15180522p1524192 >> 6.html >> Sent from the Shale - User mailing list archive at Nabble.com. >> >> >> >> >> 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. >> >> > > -- > View this message in context: > > 0.html > Sent from the Shale - User mailing list archive at Nabble.com. > > > > > 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. > > -- View this message in context: http://www.nabble.com/Problem-with-navigation-handler-tp15180522p1533542 1.html Sent from the Shale - User mailing list archive at Nabble.com. 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. |
|
|
RE: Problem with navigation handler
by samju
::
Rate this Message:
mario, if this work now so its fine:-)
|
|
|
RE: Problem with navigation handler
by mario.buonopane
::
Rate this Message:
Sam, in this way does work. What I can't do is:
- set on the action a logical action name (outcome). For example "ACT1" - configure on the dialog of shale the action (test_stateless$ricercaSinistro.DialogAction) associated to transition "ACT1" - let the action return null -----Original Message----- From: samju [mailto:julsamusa@...] Sent: 8 febbraio 2008 09.20 To: user@... Subject: RE: Problem with navigation handler mario, if this work now so its fine:-) mario.buonopane wrote: > > Yes Sam, I decided that for all AJAX Actions I don't use Dialog Manager > features but in the page I call directly the action, for example in my > button: > #{test_stateless$ricercaSinistro.nonDialogAction } > > and the action return null. > > What do you think? > > Thanks, Mario > > -----Original Message----- > From: samju [mailto:julsamusa@...] > Sent: 7 febbraio 2008 16.01 > To: user@... > Subject: RE: Problem with navigation handler > > > any progress mario? > Sam > > mario.buonopane wrote: >> >> So, in the JSP I call directly the action, for example in my button: >> #{test_stateless$ricercaSinistro.nonDialogAction } >> >> Mario >> >> -----Original Message----- >> From: samju [mailto:julsamusa@...] >> Sent: 4 febbraio 2008 14.27 >> To: user@... >> Subject: RE: Problem with navigation handler >> >> >> 1- findClaim() do return the Transition "OK" >> 2- for your ajax call we do not have to use dialog conf. stuff. work >> outside >> the Dialog >> so return null from non-Dialog action! >> >> public String nonDialogAction(){ >> >> prepare the ajax call >> /*as you mentioned befor the output schould be null*/ >> >> return null; >> /* will let us refresh the last Dialog-State-View. This View is the >> Transition outcome "OK" from a dialog-Action*/ >> } >> >> public String dialogAction(){ >> .....do smth.. >> return OK; >> } >> >> Sam >> >> >> mario.buonopane wrote: >>> >>> I'm sorry, but I don't understand.... >>> If I return null from the action, how can Shale go do transition >> ? >>> >>> >>> >>> >>> -----Original Message----- >>> From: samju [mailto:julsamusa@...] >>> Sent: 2 febbraio 2008 12.25 >>> To: user@... >>> Subject: Re: Problem with navigation handler >>> >>> >>> Your aim is to apply a ajax call on ricercaSinistro.jsp. >>> If i got what you means, I think you may do the follow: >>> >>> The outcome of the Ajax-Call-action can (should )return null. >>> This Ajax action should be handle outside the Dialog Configuration >> File. >>> (we >>> can mix dialog and non dialog action). >>> >>> The Pre-Action-State should have as target the dialog End-State. >>> >>> <action name="actionRicerca" >>> method="#{ test_stateless$ricercaSinistro.findClaim }"> >>> <transition outcome="OK" target="Exit" /> >>> </action> >>> >>> <view name="ricercaPage" viewId="/test_stateless/ricercaSinistro.jsp >> "> >>> In this View State we can call an Ajax action with the needed null >>> outcome. >>> <transition outcome=" exitdialogaction" target=" exitdialog " /> >>> >>> </view> >>> <end name=exit viewId="/test_stateless/ricercaSinistro.jsp"> >>> <end name=exitdialog viewId="/test_stateless/home.jsp"> >>> >>> I hope this will help >>> >>> >>> mario.buonopane 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". >>>> >>>> >>>> >>>> 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. >>>> >>>> >>> >>> -- >>> View this message in context: >>> >> > >>> 6.html >>> Sent from the Shale - User mailing list archive at Nabble.com. >>> >>> >>> >>> >>> 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 >> the >>> original. Any other use of the email by you is prohibited. >>> >>> >> >> -- >> View this message in context: >> > http://www.nabble.com/Problem-with-navigation-handler-tp15180522p1526807 >> 0.html >> Sent from the Shale - User mailing list archive at Nabble.com. >> >> >> >> >> 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. >> >> > > -- > View this message in context: > > 1.html > Sent from the Shale - User mailing list archive at Nabble.com. > > > > > 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. > > -- View this message in context: http://www.nabble.com/Problem-with-navigation-handler-tp15180522p1535111 2.html Sent from the Shale - User mailing list archive at Nabble.com. 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. |
|
|
RE: Problem with navigation handler
by samju
::
Rate this Message:
i need more specific details
is your aim to link-up 2 action? to let a Dialog action (outcome = ACT1") delegate to non Dialog action (outcome =null)? Sam
|
|
|
RE: Problem with navigation handler
by mario.buonopane
::
Rate this Message:
Sam, what o wanna do is:
- have a button on the page with the action attribute setted to "ACT1" - have a dialog with the association from my view to action ACT1 setted to test_stateless$ricercaSinistro.findClaim - have the findClaim method of Managed Bean test_stateless$ricercaSinistro that return null. In this case I expect that after the execution of findClaim method, the application show the same view that requested the action ACT1. Thanks Mario -----Original Message----- From: samju [mailto:julsamusa@...] Sent: 11 febbraio 2008 09.50 To: user@... Subject: RE: Problem with navigation handler i need more specific details is your aim to link-up 2 action? to let a Dialog action (outcome = ACT1") delegate to non Dialog action (outcome =null)? Sam mario.buonopane wrote: > > Sam, in this way does work. What I can't do is: > - set on the action a logical action name (outcome). For example "ACT1" > - configure on the dialog of shale the action > (test_stateless$ricercaSinistro.DialogAction) associated to transition > "ACT1" > - let the action return null > > > > -----Original Message----- > From: samju [mailto:julsamusa@...] > Sent: 8 febbraio 2008 09.20 > To: user@... > Subject: RE: Problem with navigation handler > > > mario, if this work now so its fine:-) > > mario.buonopane wrote: >> >> Yes Sam, I decided that for all AJAX Actions I don't use Dialog > Manager >> features but in the page I call directly the action, for example in >> button: >> #{test_stateless$ricercaSinistro.nonDialogAction } >> >> and the action return null. >> >> What do you think? >> >> Thanks, Mario >> >> -----Original Message----- >> From: samju [mailto:julsamusa@...] >> Sent: 7 febbraio 2008 16.01 >> To: user@... >> Subject: RE: Problem with navigation handler >> >> >> any progress mario? >> Sam >> >> mario.buonopane wrote: >>> >>> So, in the JSP I call directly the action, for example in my button: >>> #{test_stateless$ricercaSinistro.nonDialogAction } >>> >>> Mario >>> >>> -----Original Message----- >>> From: samju [mailto:julsamusa@...] >>> Sent: 4 febbraio 2008 14.27 >>> To: user@... >>> Subject: RE: Problem with navigation handler >>> >>> >>> 1- findClaim() do return the Transition "OK" >>> 2- for your ajax call we do not have to use dialog conf. stuff. work >>> outside >>> the Dialog >>> so return null from non-Dialog action! >>> >>> public String nonDialogAction(){ >>> >>> prepare the ajax call >>> /*as you mentioned befor the output schould be null*/ >>> >>> return null; >>> /* will let us refresh the last Dialog-State-View. This View is the >>> Transition outcome "OK" from a dialog-Action*/ >>> } >>> >>> public String dialogAction(){ >>> .....do smth.. >>> return OK; >>> } >>> >>> Sam >>> >>> >>> mario.buonopane wrote: >>>> >>>> I'm sorry, but I don't understand.... >>>> If I return null from the action, how can Shale go do transition > "OK" >>> ? >>>> >>>> >>>> >>>> >>>> -----Original Message----- >>>> From: samju [mailto:julsamusa@...] >>>> Sent: 2 febbraio 2008 12.25 >>>> To: user@... >>>> Subject: Re: Problem with navigation handler >>>> >>>> >>>> Your aim is to apply a ajax call on ricercaSinistro.jsp. >>>> If i got what you means, I think you may do the follow: >>>> >>>> The outcome of the Ajax-Call-action can (should )return null. >>>> This Ajax action should be handle outside the Dialog Configuration >>> File. >>>> (we >>>> can mix dialog and non dialog action). >>>> >>>> The Pre-Action-State should have as target the dialog End-State. >>>> >>>> <action name="actionRicerca" >>>> method="#{ test_stateless$ricercaSinistro.findClaim }"> >>>> <transition outcome="OK" target="Exit" /> >>>> </action> >>>> >>>> <view name="ricercaPage" >>> "> >>>> In this View State we can call an Ajax action with the needed null >>>> outcome. >>>> <transition outcome=" exitdialogaction" target=" exitdialog " /> >>>> >>>> </view> >>>> <end name=exit viewId="/test_stateless/ricercaSinistro.jsp"> >>>> <end name=exitdialog viewId="/test_stateless/home.jsp"> >>>> >>>> I hope this will help >>>> >>>> >>>> mario.buonopane 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}" >>>> null >>>>> I have a loop because the control remain to the view "ricercaPage" >>> and >>>>> call again the outcome "ricerca". >>>>> >>>>> >>>>> >>>>> 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. >>>>> >>>>> >>>> >>>> -- >>>> View this message in context: >>>> >>> >> > >>>> 6.html >>>> Sent from the Shale - User mailing list archive at Nabble.com. >>>> >>>> >>>> >>>> >>>> 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. >>>> >>>> >>> >>> -- >>> View this message in context: >>> >> > >>> 0.html >>> Sent from the Shale - User mailing list archive at Nabble.com. >>> >>> >>> >>> >>> 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 >> the >>> original. Any other use of the email by you is prohibited. >>> >>> >> >> -- >> View this message in context: >> > http://www.nabble.com/Problem-with-navigation-handler-tp15180522p1533542 >> 1.html >> Sent from the Shale - User mailing list archive at Nabble.com. >> >> >> >> >> 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. >> >> > > -- > View this message in context: > > 2.html > Sent from the Shale - User mailing list archive at Nabble.com. > > > > > 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. > > -- View this message in context: http://www.nabble.com/Problem-with-navigation-handler-tp15180522p1540753 0.html Sent from the Shale - User mailing list archive at Nabble.com. 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. |
| Free embeddable forum powered by Nabble | Forum Help |
