RE: No onException called
Rahul, every time I ask for something someone respond me ask me for a use case, but the point is: Why don't throw a framework-specific exception like "TransitionNotFoundException"? Is so horrible? In my point of view, if a framework throw specific exception would be a good idea... Craig told me the same think, so if you agree I can open an RFC. However thanks for Shale and the time you spend for it! Mario -Original Message- From: Rahul Akolkar [mailto:[EMAIL PROTECTED] Sent: 4 giugno 2007 22.05 To: user@shale.apache.org Subject: Re: No onException called On 6/4/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Rahul, some times ago Craig told me that the onException is the correct > way to catch and manage this exception: > http://www.mail-archive.com/user@shale.apache.org/msg0.html > The code will throw an IllegalStateException (as you've posted in the top post in this thread), but won't result in an onException callback in this scenario (I'm sort of interested in knowing what the scenarios are -- other than developer error). Obviously, I can't speak for Craig or anyone else, but I think his response in this thread overrides that one by virtue of being more recent. -Rahul > Mario > > -Original Message- > From: Rahul Akolkar [mailto:[EMAIL PROTECTED] > Sent: 30 maggio 2007 18.20 > To: user@shale.apache.org > Subject: Re: No onException called > > On 5/30/07, [EMAIL PROTECTED] > <[EMAIL PROTECTED]> wrote: > > Hi, I have configure a my dialogContextListener but If I receive the > > onEntry method call back (for example) but I don't receive any > > onException in case I call a transition not setted in dialog config > > file. In the log I found: > > > > > The DialogContextListeners are notified on certain type of application > errors such as: > > * Exception while executing the method binding expression associated > with an action state > * Exception while trying to instantiate dialog data > > but are not notified on exceptions that have to do with either the > completeness of the dialog's "model" (such as the case here, an > unknown transition) or dialog lifecycle error conditions. > > I suspect it might have to do with the latter being perceived as > fatal. Craig will know. > > -Rahul > 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: SHALE-409 fix
Any news about the fix?
-Original Message-
From: Gary VanMatre [mailto:[EMAIL PROTECTED]
Sent: 23 maggio 2007 22.44
To: user@shale.apache.org
Subject: Re: SHALE-409 fix
>From: "Craig McClanahan" <[EMAIL PROTECTED]>
>
> On 5/23/07, Gary VanMatre wrote:
> > >From: "Craig McClanahan"
> > >
> > > On 5/23/07, Gary VanMatre wrote:
> > > >
> > > > >From: Torsten Krah [EMAIL PROTECTED]
> > > > >
> > > > >The question would be - as the second run is really useless -
how to
> > > > >identify annotated tiger beans.
> > > > >If they can be identified (dont know if this is possible and
how to do
> > > > >it yet), than the code in run two can be fixed to do what the
comment
> > > > >does want to do, remove them, instead of removing the rest
completely.
> > > > >
> > > >
> > > > I'm thinking that we could just remove that bit of logic because
the
> > > > web container should fire the ServletRequestListener [1]
regardless?
> > > >
> > >
> > > It will indeed get called later, but outside the JSF lifecycle ...
> > > which means you would not be able to get to the FacesContext in a
> > > destroy() method. That's why this logic was inserted in the first
> > > place.
> > >
> >
> > Ah, I figured there was good reason. What if we delegated to the
tiger
> > LifecycleListener from the JSF phase listener - same pattern?
> >
> >
> > // Delegate to the Tiger Extensions instance if it exists
> > LifecycleListener tiger = tiger();
> > if (tiger != null) {
> > tiger.contextDestroyed(event);
> > }
> >
> >
> > private LifecycleListener tiger() ...
> >
>
> At first blush this looks good, but I'm heads down getting ready for a
> trip to India next week, so I won't be able to actually play with this
> until the first week of June.
>
Cool. I'll try to take a look this week. I don't have a Solaris box
sitting around to test but I could make the change to the 1.1.0-SNAPSHOT
and we could decide if we want to push it to the other branch later on.
> Craig
>
Gary
> >
> >
> > > Craig
> > >
> >
> > Gary
> >
> > > > However, there might be a funky case that resulted in this logic
in the
> > > > PhaseListener - not sure.
> > > >
> > > > [1]
> > > >
> > >
>
http://svn.apache.org/viewvc/shale/framework/trunk/shale-view/src/main/j
ava/org/
> > > apache/shale/view/faces/LifecycleListener.java?view=markup
> > > >
> > > >
> > > > >Torsten
> > > >
> > > > Gary
> > > >
> > > >
> > > >
> > > > -- Forwarded message --
> > > > From: Torsten Krah
> > > > To: user@shale.apache.org
> > > > Date: Wed, 23 May 2007 19:11:48 +
> > > > Subject: Re: SHALE-409 fix
> > > > The question would be - as the second run is really useless -
how to
> > > > identify annotated tiger beans.
> > > > If they can be identified (dont know if this is possible and how
to do
> > > > it yet), than the code in run two can be fixed to do what the
comment
> > > > does want to do, remove them, instead of removing the rest
completely.
> > > >
> > > > Torsten
> > > >
> > > >
> > > > Am Dienstag, den 22.05.2007, 15:41 +0200 schrieb
> > > > [EMAIL PROTECTED]:
> > > > > Please fix the bug SHALE-409.
> > > > >
> > > > >
> > > > >
> > > > > Regards
> > > > >
> > > > > Mario Buonopane
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > 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.
> > > >
> > > >
> > > >
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.
Problem with subdialogs
I have some problem with subdialogs using shale1.1.0-snapshot (22/05). The first problem is: I have a dialog B with following this configuration: When I run this dialog not how subdialog I need this dialog end showing "/home/home.jsp". I also need to call this dialog like subdialog of the following dialog C: The problem is that when the subdialog B ends, shale does not show /test_dialogo_a/pagina_b.jsp but show "/home/home.jsp" . When I use old shale 1.0.3 does work correctly. The second problem is that I'm using the "data" property of DialogContext to store some information but when start subdialog B, the getData of DialogContext return an HashMap (not my class). Please help me. Mario
Cannot set my JSF-Components
Hi @ all, at first sorry for my poor English. I'm using shale for few month and at least i have a problem with a simple textinput. I type any string in my jsf-component, but my method gets only null values :-(. Here are my files: Java class, which should get the values from the jsf-components. The method setup exits with the string "failed", cause toid == null. http://www.nabble.com/file/p10970838/EditTransmitAction.java EditTransmitAction.java JSF-File, profile$transmit is mapped to EditTransmitAction class. The transmit button was clicked http://www.nabble.com/file/p10970838/transaction.jsp transaction.jsp Only the last dialog "Transfer" is interesting for this process. http://www.nabble.com/file/p10970838/dialog-config.xml dialog-config.xml And the full faces-configxml: http://www.nabble.com/file/p10970838/faces-config.xml faces-config.xml If i start the setup method of the EditTransmitAction class, i get this log: init0 init1 setup null, null, null <--- This are my values Noticeable is that the init method was started twice. So i think that i get two different EditTransmitAction objects. How can i solve this problem? Thanks for every help. Bye Pawel -- View this message in context: http://www.nabble.com/Cannot-set-my-JSF-Components-tf3872171.html#a10970838 Sent from the Shale - User mailing list archive at Nabble.com.
Is there any one?
This project seems to be deadi'm very afraid! Is there some one can help me? Mario Buonopane Accenture Insurance Services & Systems Via C. Colombo 112, 00147 Roma Tel: +39 06 51566543 Mobile: +39 334 6563433 Fax: +39 06 51566550 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: Is there any one?
>From: <[EMAIL PROTECTED]> > > This project seems to be deadi'm very afraid! > > Is there some one can help me? > It's not dead, I think this is just a busy time for everyone. What's your problem? Gary > > > Mario Buonopane > Accenture Insurance Services & Systems > Via C. Colombo 112, 00147 Roma > Tel: +39 06 51566543 > Mobile: +39 334 6563433 > Fax: +39 06 51566550 > > > > > > 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 subdialogs
I have tried to set end state of dialog B without setting viewId. On
shale internet site there is this sentence:
"If no view identifier was configured (meaning that the parent dialog
will be responsible for rendering the response to the current request),
simply return the logical outcome that caused this EndState to be
selected"
This does not resolve the problem because the application continue to
state to test_dialogo_b/pagina_c.jsp (last view of dialog B). If I call
the dialog B not in subdialog, I expect that at the end of dialog B
shale will call the outcome "avanti" (last transition outcome) but does
not happens! Analyzing the code of
org.apache.shale.dialog.faces.DialogNavigationHandler this is the point
called in end state transition:
dcontext.advance(context, outcome);
if (log.isDebugEnabled()) {
log.debug("Advancing dialog '"
+ dcontext.getName() + "' for FacesContext '"
+ context + "' with navigation to viewId '"
+ context.getViewRoot().getViewId() + "'");
}
dcontext.advance does not call any view (I did not configure) and does
not call any outcome may be, in case of viewId not setted, should
call:
original.handleNavigation(context, fromAction, outcome);
?
???
Mario
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: 5 giugno 2007 14.43
To: user@shale.apache.org
Subject: Problem with subdialogs
I have some problem with subdialogs using shale1.1.0-snapshot (22/05).
The first problem is:
I have a dialog B with following this configuration:
When I run this dialog not how subdialog I need this dialog end showing
"/home/home.jsp".
I also need to call this dialog like subdialog of the following dialog
C:
The problem is that when the subdialog B ends, shale does not show
/test_dialogo_a/pagina_b.jsp but show "/home/home.jsp" .
When I use old shale 1.0.3 does work correctly.
The second problem is that I'm using the "data" property of
DialogContext to store some information but when start subdialog B, the
getData of DialogContext return an HashMap (not my class).
Please help me.
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: Is there any one?
Please Gary, read my mail regarding problems with subdialogs... Thanks Mario -Original Message- From: Gary VanMatre [mailto:[EMAIL PROTECTED] Sent: 5 giugno 2007 17.28 To: user@shale.apache.org Subject: Re: Is there any one? >From: <[EMAIL PROTECTED]> > > This project seems to be deadi'm very afraid! > > Is there some one can help me? > It's not dead, I think this is just a busy time for everyone. What's your problem? Gary > > > Mario Buonopane > Accenture Insurance Services & Systems > Via C. Colombo 112, 00147 Roma > Tel: +39 06 51566543 > Mobile: +39 334 6563433 > Fax: +39 06 51566550 > > > > > > 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. > 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 subdialogs
>From: <[EMAIL PROTECTED]>
>
> I have tried to set end state of dialog B without setting viewId. On
> shale internet site there is this sentence:
>
> "If no view identifier was configured (meaning that the parent dialog
> will be responsible for rendering the response to the current request),
> simply return the logical outcome that caused this EndState to be
> selected"
>
> This does not resolve the problem because the application continue to
> state to test_dialogo_b/pagina_c.jsp (last view of dialog B). If I call
> the dialog B not in subdialog, I expect that at the end of dialog B
> shale will call the outcome "avanti" (last transition outcome) but does
> not happens! Analyzing the code of
> org.apache.shale.dialog.faces.DialogNavigationHandler this is the point
> called in end state transition:
> dcontext.advance(context, outcome);
> if (log.isDebugEnabled()) {
> log.debug("Advancing dialog '"
> + dcontext.getName() + "' for FacesContext '"
> + context + "' with navigation to viewId '"
> + context.getViewRoot().getViewId() + "'");
> }
>
> dcontext.advance does not call any view (I did not configure) and does
> not call any outcome may be, in case of viewId not setted, should
> call:
> original.handleNavigation(context, fromAction, outcome);
> ?
> ???
>
The shale dialog navigation uses JSF navigation rules defined in the
faces-config.xml.
Do you have navigation rules for the viewId with outcomes for the view in
question?
When the navigation handler can not find a match rule for the "outcome", it
re-renders the current view.
> Mario
>
>
Gary
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> Sent: 5 giugno 2007 14.43
> To: user@shale.apache.org
> Subject: Problem with subdialogs
>
> I have some problem with subdialogs using shale1.1.0-snapshot (22/05).
>
> The first problem is:
>
>
>
> I have a dialog B with following this configuration:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> When I run this dialog not how subdialog I need this dialog end showing
> "/home/home.jsp".
>
> I also need to call this dialog like subdialog of the following dialog
> C:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> >
> target="Pagina B"/>
>
> >
> target="Pagina A"/>
>
>
>
>
>
>
>
>
>
>
>
>
>
> The problem is that when the subdialog B ends, shale does not show
> /test_dialogo_a/pagina_b.jsp but show "/home/home.jsp" .
>
>
>
> When I use old shale 1.0.3 does work correctly.
>
>
>
> The second problem is that I'm using the "data" property of
> DialogContext to store some information but when start subdialog B, the
> getData of DialogContext return an HashMap (not my class).
>
>
>
> Please help me.
>
>
>
> 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 subdialogs
Yes I have:
avanti
/home/home.jsp
Of my faces-config.xml.
But if you look at the code I have attached,
org.apache.shale.dialog.faces.DialogNavigationHandler call advance on
dcontext (BasicDialogContext). BasicDialogContext.advance, in case the
viewId is null, return without call any view and DialogNavigationHandler
does not call original.handleNavigation(context, fromAction, outcome)...
Mario
-Original Message-
From: Gary VanMatre [mailto:[EMAIL PROTECTED]
Sent: 5 giugno 2007 17.49
To: user@shale.apache.org
Subject: RE: Problem with subdialogs
>From: <[EMAIL PROTECTED]>
>
> I have tried to set end state of dialog B without setting viewId. On
> shale internet site there is this sentence:
>
> "If no view identifier was configured (meaning that the parent dialog
> will be responsible for rendering the response to the current
request),
> simply return the logical outcome that caused this EndState to be
> selected"
>
> This does not resolve the problem because the application continue to
> state to test_dialogo_b/pagina_c.jsp (last view of dialog B). If I
call
> the dialog B not in subdialog, I expect that at the end of dialog B
> shale will call the outcome "avanti" (last transition outcome) but
does
> not happens! Analyzing the code of
> org.apache.shale.dialog.faces.DialogNavigationHandler this is the
point
> called in end state transition:
> dcontext.advance(context, outcome);
> if (log.isDebugEnabled()) {
> log.debug("Advancing dialog '"
> + dcontext.getName() + "' for FacesContext '"
> + context + "' with navigation to viewId '"
> + context.getViewRoot().getViewId() + "'");
> }
>
> dcontext.advance does not call any view (I did not configure) and does
> not call any outcome may be, in case of viewId not setted, should
> call:
> original.handleNavigation(context, fromAction, outcome);
> ?
> ???
>
The shale dialog navigation uses JSF navigation rules defined in the
faces-config.xml.
Do you have navigation rules for the viewId with outcomes for the view
in question?
When the navigation handler can not find a match rule for the "outcome",
it re-renders the current view.
> Mario
>
>
Gary
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> Sent: 5 giugno 2007 14.43
> To: user@shale.apache.org
> Subject: Problem with subdialogs
>
> I have some problem with subdialogs using shale1.1.0-snapshot (22/05).
>
> The first problem is:
>
>
>
> I have a dialog B with following this configuration:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> When I run this dialog not how subdialog I need this dialog end
showing
> "/home/home.jsp".
>
> I also need to call this dialog like subdialog of the following dialog
> C:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> >
> target="Pagina B"/>
>
> >
> target="Pagina A"/>
>
>
>
>
>
>
>
>
>
>
>
>
>
> The problem is that when the subdialog B ends, shale does not show
> /test_dialogo_a/pagina_b.jsp but show "/home/home.jsp" .
>
>
>
> When I use old shale 1.0.3 does work correctly.
>
>
>
> The second problem is that I'm using the "data" property of
> DialogContext to store some information but when start subdialog B,
the
> getData of DialogContext return an HashMap (not my class).
>
>
>
> Please help me.
>
>
>
> 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.
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: Is there any one?
On 6/5/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: This project seems to be deadi'm very afraid! If you mean "dead tired", that would definitely describe me! :-). I have been at three conferences in a row the last three weeks (including last week in India), with zero time to do any coding at all, and am now back with a *mountain* of back email and other stuff to catch up on. Please be a little patient :-). Craig Is there some one can help me? Mario Buonopane Accenture Insurance Services & Systems Via C. Colombo 112, 00147 Roma Tel: +39 06 51566543 Mobile: +39 334 6563433 Fax: +39 06 51566550 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: No onException called
On 6/5/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: Rahul, every time I ask for something someone respond me ask me for a use case, Sorry if it seems that way, but in this particular thread I think "the larger picture" should drive any code changes, and I thought it'd be better understood once we put some usecases on the table. In other words, we could: o Define a new exception * As you indicate below * But I'm sure there are other error conditions (such as refering to a non-existent state) - Should that be another exception type? - Should there be one generic "DialogException"? o Channel these errors via onException() callbacks (as you originally seemed to suggest) * Should the dialog be determinated? * Should the dialog remain in the current state (and wait for further input)? So, some thought needs to be given to the design so we have a lasting congruous solution for all types of dialog error handling. Code changes can then quickly follow. but the point is: Why don't throw a framework-specific exception like "TransitionNotFoundException"? Is so horrible? In my point of view, if a framework throw specific exception would be a good idea... Craig told me the same think, so if you agree I can open an RFC. Sure sounds like an option (and presumably works sufficiently well for all your usecases as well). You don't need me to agree before you open any RFC, please feel free to open any tickets at will ;-) -Rahul However thanks for Shale and the time you spend for it! Mario
Re: Problem with subdialogs
Comments inline (quite a ways down) ... On 6/5/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: I have some problem with subdialogs using shale1.1.0-snapshot (22/05). The first problem is: I have a dialog B with following this configuration: When I run this dialog not how subdialog I need this dialog end showing "/home/home.jsp". Which should be happening, correct? I also need to call this dialog like subdialog of the following dialog C: The problem is that when the subdialog B ends, shale does not show /test_dialogo_a/pagina_b.jsp but show "/home/home.jsp" . When I use old shale 1.0.3 does work correctly. Looks like a bug to me, seems related to SHALE-423 [1]. I will take a look at this, hopefully this weekend. The second problem is that I'm using the "data" property of DialogContext to store some information but when start subdialog B, the getData of DialogContext return an HashMap (not my class). I haven't used the basic dialog implementation heavily, but that matches my understanding of how the basic impl works. A subdialog also implies a new dialog data being "pushed onto the stack" (and if you haven't specified a dialog data class, it defaults to a HashMap). This is different from the Commons SCXML implementation, where the dialog data will be shared between the parent dialog and any subdialogs (to whatever "depth" they may exist). I believe you are looking for something similar, though that is not how the basic impl behaves (there are pros/cons to either). -Rahul [1] http://issues.apache.org/struts/browse/SHALE-423 Please help me. Mario
Re: Problem with subdialogs
On 6/5/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: Yes I have: avanti /home/home.jsp Of my faces-config.xml. Hold off on mix and matching faces-config navigation rules and dialog configurations. This shouldn't be necessary, atleast in the dialogs you've posted. It seems there is either a bug or the documentation you quote does not match the behavior. In any case, as I said, I'll try to track it down this weekend. -Rahul But if you look at the code I have attached, org.apache.shale.dialog.faces.DialogNavigationHandler call advance on dcontext (BasicDialogContext). BasicDialogContext.advance, in case the viewId is null, return without call any view and DialogNavigationHandler does not call original.handleNavigation(context, fromAction, outcome)... Mario
RE: Is there any one?
Sure Craigi'll patient :)! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Craig McClanahan Sent: 5 giugno 2007 19.09 To: user@shale.apache.org Subject: Re: Is there any one? On 6/5/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > This project seems to be deadi'm very afraid! > If you mean "dead tired", that would definitely describe me! :-). I have been at three conferences in a row the last three weeks (including last week in India), with zero time to do any coding at all, and am now back with a *mountain* of back email and other stuff to catch up on. Please be a little patient :-). Craig > Is there some one can help me? > > > > Mario Buonopane > Accenture Insurance Services & Systems > Via C. Colombo 112, 00147 Roma > Tel: +39 06 51566543 > Mobile: +39 334 6563433 > Fax: +39 06 51566550 > > > > > > 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. > 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 subdialogs
On 6/5/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: I have some problem with subdialogs using shale1.1.0-snapshot (22/05). Could you try the 20070605 build from here [1] (or try building yourself). I've made a change few minutes ago. -Rahul [1] http://people.apache.org/builds/shale/nightly/
