You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by "David Sean Taylor (JIRA)" <je...@portals.apache.org> on 2008/10/10 23:31:44 UTC
[jira] Created: (JS2-908) Transactional Isolation on Portlet
Application Deployment
Transactional Isolation on Portlet Application Deployment
---------------------------------------------------------
Key: JS2-908
URL: https://issues.apache.org/jira/browse/JS2-908
Project: Jetspeed 2
Issue Type: Improvement
Components: Deployment
Affects Versions: 2.2
Reporter: David Sean Taylor
Assignee: David Sean Taylor
Fix For: 2.2
Make the Portlet Application Manager deployment APIs transactional (start, stop, register, unregister). Deploying a portlet application currently is implemented across several Spring components, requiring atomic commits across registry, permissions, roles, etc. Transactional isolation is also required in order to ensure that other threads don't hit temporarily deleted registry objects before they can be re-registered.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Resolved: (JS2-908) Transactional Isolation on Portlet
Application Deployment
Posted by "David Sean Taylor (JIRA)" <je...@portals.apache.org>.
[ https://issues.apache.org/jira/browse/JS2-908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Sean Taylor resolved JS2-908.
-----------------------------------
Resolution: Fixed
Applied and tested.
> Transactional Isolation on Portlet Application Deployment
> ---------------------------------------------------------
>
> Key: JS2-908
> URL: https://issues.apache.org/jira/browse/JS2-908
> Project: Jetspeed 2
> Issue Type: Improvement
> Components: Deployment
> Affects Versions: 2.2
> Reporter: David Sean Taylor
> Assignee: David Sean Taylor
> Fix For: 2.2
>
>
> Make the Portlet Application Manager deployment APIs transactional (start, stop, register, unregister). Deploying a portlet application currently is implemented across several Spring components, requiring atomic commits across registry, permissions, roles, etc. Transactional isolation is also required in order to ensure that other threads don't hit temporarily deleted registry objects before they can be re-registered.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org