You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@shindig.apache.org by "Dan Dumont (JIRA)" <ji...@apache.org> on 2012/06/18 21:31:42 UTC
[jira] [Created] (SHINDIG-1805) Better error handling around
container token refreshes.
Dan Dumont created SHINDIG-1805:
-----------------------------------
Summary: Better error handling around container token refreshes.
Key: SHINDIG-1805
URL: https://issues.apache.org/jira/browse/SHINDIG-1805
Project: Shindig
Issue Type: Improvement
Reporter: Dan Dumont
It would be nice to be able to specify return a fatal error in the container token refresh for when a new container token is not likely to be returned. The container can then run queued up callbacks with an error message so that they can handle the error appropriately (stop a spinner and display an error message, perhaps)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (SHINDIG-1805) Better error handling around
container token refreshes.
Posted by "Ryan Baxter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ryan Baxter reassigned SHINDIG-1805:
------------------------------------
Assignee: Dan Dumont
> Better error handling around container token refreshes.
> -------------------------------------------------------
>
> Key: SHINDIG-1805
> URL: https://issues.apache.org/jira/browse/SHINDIG-1805
> Project: Shindig
> Issue Type: Improvement
> Reporter: Dan Dumont
> Assignee: Dan Dumont
> Fix For: 2.5.0
>
>
> It would be nice to be able to specify return a fatal error in the container token refresh for when a new container token is not likely to be returned. The container can then run queued up callbacks with an error message so that they can handle the error appropriately (stop a spinner and display an error message, perhaps)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SHINDIG-1805) Better error handling around
container token refreshes.
Posted by "Ryan Baxter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ryan Baxter updated SHINDIG-1805:
---------------------------------
Fix Version/s: 2.5.0-beta3
> Better error handling around container token refreshes.
> -------------------------------------------------------
>
> Key: SHINDIG-1805
> URL: https://issues.apache.org/jira/browse/SHINDIG-1805
> Project: Shindig
> Issue Type: Improvement
> Reporter: Dan Dumont
> Assignee: Dan Dumont
> Fix For: 2.5.0, 2.5.0-beta3
>
>
> It would be nice to be able to specify return a fatal error in the container token refresh for when a new container token is not likely to be returned. The container can then run queued up callbacks with an error message so that they can handle the error appropriately (stop a spinner and display an error message, perhaps)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SHINDIG-1805) Better error handling around
container token refreshes.
Posted by "Ryan Baxter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ryan Baxter updated SHINDIG-1805:
---------------------------------
Fix Version/s: 2.5.0
> Better error handling around container token refreshes.
> -------------------------------------------------------
>
> Key: SHINDIG-1805
> URL: https://issues.apache.org/jira/browse/SHINDIG-1805
> Project: Shindig
> Issue Type: Improvement
> Reporter: Dan Dumont
> Assignee: Dan Dumont
> Fix For: 2.5.0
>
>
> It would be nice to be able to specify return a fatal error in the container token refresh for when a new container token is not likely to be returned. The container can then run queued up callbacks with an error message so that they can handle the error appropriately (stop a spinner and display an error message, perhaps)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (SHINDIG-1805) Better error handling around
container token refreshes.
Posted by "Dan Dumont (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Dumont resolved SHINDIG-1805.
---------------------------------
Resolution: Fixed
Committed r1351468
> Better error handling around container token refreshes.
> -------------------------------------------------------
>
> Key: SHINDIG-1805
> URL: https://issues.apache.org/jira/browse/SHINDIG-1805
> Project: Shindig
> Issue Type: Improvement
> Reporter: Dan Dumont
>
> It would be nice to be able to specify return a fatal error in the container token refresh for when a new container token is not likely to be returned. The container can then run queued up callbacks with an error message so that they can handle the error appropriately (stop a spinner and display an error message, perhaps)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira