breaking out of a dialog

[Comerford, Sean]

Let's say my user is in step 3 or 5 part dialog.

For whatever reason, he decides to do something else within in the current
app and enters an appropriate URL into the browser's location field.

The new page (not part of the dialog) loads fine but if the user attempts to
click anything invoking a JSF action, it results in an error:

    javax.servlet.ServletException: You have requested a transition outcome
    named "success" from a state named "page 2" in a dialog named "test
    dialog", but no transition definition can be found.  Double check the
    spelling of the transition outcome name.

So the question is:

how can I prevent this?

Or Is a shale dialog ALWAYS in effect until a dialog defined exit outcome
occurs (hope not!)?

--
Sean Comerford, Software Engineer
Major League Baseball Advanced Media
sean.comerford@... ~ 212.485.4508




************************
MLB.com: Where Baseball is Always On

[Wendy Smoak-3]

On 7/27/06, Sean Comerford <Sean.Comerford@...> wrote:

> For whatever reason, he decides to do something else within in the current
> app and enters an appropriate URL into the browser's location field.
>
> The new page (not part of the dialog) loads fine but if the user attempts to
> click anything invoking a JSF action, it results in an error:

There are some known issues with dialog state.  Here's a link to the
component in JIRA... do any of these seem to apply?
http://tinyurl.com/rgv3w

--
Wendy

[Adam Brod-4]

I believe the is the main outstanding bug in Shale Dialogs right now.
(There is also a problem if you are in a Dialog and you hit the back
button).  I've run into the same problem, so we stopped using Dialogs.
However, the other Shale frameworks are great.

You might want to consider JBoss Seam for similar functionality to Shale
Dialog.

Adam Brod
Product Development Team


"Sean Comerford" <Sean.Comerford@...>
07/27/2006 02:58 PM
Please respond to
user@...


To
"user@..." <user@...>
cc

Subject
breaking out of a dialog






Let's say my user is in step 3 or 5 part dialog.

For whatever reason, he decides to do something else within in the current
app and enters an appropriate URL into the browser's location field.

The new page (not part of the dialog) loads fine but if the user attempts
to
click anything invoking a JSF action, it results in an error:

    javax.servlet.ServletException: You have requested a transition
outcome
    named "success" from a state named "page 2" in a dialog named "test
    dialog", but no transition definition can be found.  Double check the
    spelling of the transition outcome name.

So the question is:

how can I prevent this?

Or Is a shale dialog ALWAYS in effect until a dialog defined exit outcome
occurs (hope not!)?

--
Sean Comerford, Software Engineer
Major League Baseball Advanced Media
sean.comerford@... ~ 212.485.4508




************************
MLB.com: Where Baseball is Always On



Disclaimer: This electronic mail and any attachments are confidential and may be privileged. If you are not the intended recipient, please notify the sender immediately by replying to this email, and destroy all copies of this email and any attachments. Thank you.

[Comerford, Sean]

It sounds like SHALE-48 more or less covers it.

Any idea when this might be addressed?

Unless I'm missing something. this issue (and related ones in SHALE-48) make
dialogs more or less unusable in a production environment.

On 7/27/06 3:07 PM, "Wendy Smoak" <wsmoak@...> wrote:

> On 7/27/06, Sean Comerford <Sean.Comerford@...> wrote:
>
>> For whatever reason, he decides to do something else within in the current
>> app and enters an appropriate URL into the browser's location field.
>>
>> The new page (not part of the dialog) loads fine but if the user attempts to
>> click anything invoking a JSF action, it results in an error:
>
> There are some known issues with dialog state.  Here's a link to the
> component in JIRA... do any of these seem to apply?
> http://tinyurl.com/rgv3w

--
Sean Comerford, Software Engineer
Major League Baseball Advanced Media
sean.comerford@... ~ 212.485.4508




************************
MLB.com: Where Baseball is Always On

[schof-2]

SHALE-48 is a major problem.  Several months ago Craig and  I
discussed a potential solution.  I can't remember the details of his
proposed solution but it sounded like it might work.  I would expect
some movement on this within a few weeks because the few important
Dialog bugs are blocking the first stable release.

Sean

On 7/27/06, Sean Comerford <Sean.Comerford@...> wrote:

> It sounds like SHALE-48 more or less covers it.
>
> Any idea when this might be addressed?
>
> Unless I'm missing something. this issue (and related ones in SHALE-48) make
> dialogs more or less unusable in a production environment.
>
> On 7/27/06 3:07 PM, "Wendy Smoak" <wsmoak@...> wrote:
>
> > On 7/27/06, Sean Comerford <Sean.Comerford@...> wrote:
> >
> >> For whatever reason, he decides to do something else within in the current
> >> app and enters an appropriate URL into the browser's location field.
> >>
> >> The new page (not part of the dialog) loads fine but if the user attempts to
> >> click anything invoking a JSF action, it results in an error:
> >
> > There are some known issues with dialog state.  Here's a link to the
> > component in JIRA... do any of these seem to apply?
> > http://tinyurl.com/rgv3w
>
>
> --
> Sean Comerford, Software Engineer
> Major League Baseball Advanced Media
> sean.comerford@... ~ 212.485.4508
>
>
>
>
> ************************
> MLB.com: Where Baseball is Always On
>
>
>

[Mark_Huang]

I downloaded shale-framework-1.0.4 (the latest version). When I clicked the NON-DIALOG related link from inside the DIALOG conversion, I got the same error.

Is this bug fixed?

schof-2 wrote:

SHALE-48 is a major problem.  Several months ago Craig and  I
discussed a potential solution.  I can't remember the details of his
proposed solution but it sounded like it might work.  I would expect
some movement on this within a few weeks because the few important
Dialog bugs are blocking the first stable release.

Sean

On 7/27/06, Sean Comerford <[e-mail]> wrote:
> It sounds like SHALE-48 more or less covers it.
>
> Any idea when this might be addressed?
>
> Unless I'm missing something. this issue (and related ones in SHALE-48) make
> dialogs more or less unusable in a production environment.
>
> On 7/27/06 3:07 PM, "Wendy Smoak" <[e-mail]> wrote:
>
> > On 7/27/06, Sean Comerford <[e-mail]> wrote:
> >
> >> For whatever reason, he decides to do something else within in the current
> >> app and enters an appropriate URL into the browser's location field.
> >>
> >> The new page (not part of the dialog) loads fine but if the user attempts to
> >> click anything invoking a JSF action, it results in an error:
> >
> > There are some known issues with dialog state.  Here's a link to the
> > component in JIRA... do any of these seem to apply?
> > http://tinyurl.com/rgv3w
>
>
> --
> Sean Comerford, Software Engineer
> Major League Baseball Advanced Media
> [e-mail] ~ 212.485.4508
>
>
>
>
> ************************
> MLB.com: Where Baseball is Always On
>
>
>

[Rahul Akolkar]

On 11/7/07, Mark_Huang <mhuang_us@...> wrote:
>
> I downloaded shale-framework-1.0.4 (the latest version). When I clicked the
> NON-DIALOG related link from inside the DIALOG conversion, I got the same
> error.
>
> Is this bug fixed?
>
<snip/>

Thanks for looking through the archives. The thread you've picked up
on is more than a year old, there have been other discussions on this
topic beyond this thread. In short, this is not considered a bug.

For details, browse any archive of choice, for example:

  http://shale.markmail.org/

-Rahul

> schof-2 wrote:
> >
> > SHALE-48 is a major problem.  Several months ago Craig and  I
> > discussed a potential solution.  I can't remember the details of his
> > proposed solution but it sounded like it might work.  I would expect
> > some movement on this within a few weeks because the few important
> > Dialog bugs are blocking the first stable release.
> >
> > Sean
> >
> > On 7/27/06, Sean Comerford <Sean.Comerford@...> wrote:
> >> It sounds like SHALE-48 more or less covers it.
> >>
> >> Any idea when this might be addressed?
> >>
> >> Unless I'm missing something. this issue (and related ones in SHALE-48)
> >> make
> >> dialogs more or less unusable in a production environment.
> >>
> >> On 7/27/06 3:07 PM, "Wendy Smoak" <wsmoak@...> wrote:
> >>
> >> > On 7/27/06, Sean Comerford <Sean.Comerford@...> wrote:
> >> >
> >> >> For whatever reason, he decides to do something else within in the
> >> current
> >> >> app and enters an appropriate URL into the browser's location field.
> >> >>
> >> >> The new page (not part of the dialog) loads fine but if the user
> >> attempts to
> >> >> click anything invoking a JSF action, it results in an error:
> >> >
> >> > There are some known issues with dialog state.  Here's a link to the
> >> > component in JIRA... do any of these seem to apply?
> >> > http://tinyurl.com/rgv3w
> >>
> >>
> >> --
> >> Sean Comerford, Software Engineer
> >> Major League Baseball Advanced Media
> >> sean.comerford@... ~ 212.485.4508
> >>
> >>
> >>
> >>
> >> ************************
> >> MLB.com: Where Baseball is Always On
> >>
> >>
> >>
> >
> >
>
> --
> View this message in context: http://www.nabble.com/breaking-out-of-a-dialog-tf2011387.html#a13640230
> Sent from the Shale - User mailing list archive at Nabble.com.
>
>