[jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1906) Portlet Application deployment integration with 2.7 deployment.
Julien Viet (JIRA)
jira-events at lists.jboss.org
Wed Feb 20 14:50:42 EST 2008
[ http://jira.jboss.com/jira/browse/JBPORTAL-1906?page=all ]
Julien Viet updated JBPORTAL-1906:
----------------------------------
Description:
It covers:
- Use JBoss Portal 2.7 deployment life cycle callbacks to manage the life cycle of PC 2.0 containers.
- Integrate jboss-portlet.xml using a way that needs TBD (either separate or using the InfoFactory stuff), InfoFactory stuff is for now disabled but should be somehow reactived.
- Ugly APIFactory was removed so remove JBossPortletRequest / JBossPortletResponse. We should use the new 2.0 features to handle those uses cases (like sign out).
was:
It covers:
- Use JBoss Portal 2.7 deployment life cycle callbacks to manage the life cycle of PC 2.0 containers.
- Dissociate 2.7 jboss-portlet.xml handling from the metadata system of PC 2.0. The 2.7 integration should keep a Map of Portlet Container to metadata. Those meta data are mostly used by interceptors so interceptor should be somehow injected the service that manage the jboss-portlet.xml metadata in order to apply the correct behavior at runtime.
For instance, the TX behavior configured in jboss-portlet.xml is made available to the TransactionInterceptor and used like :
public PortletInvocationResponse invoke(PortletInvocation invocation) {
PortletContainer container = (PortletContainer)invocation.getAttribute(PortletInvocation.INVOCATION_SCOPE, PortletContainerInvoker.PORTLET_CONTAINER);
TXBehavior blah = portletContainerJBossPortletInfoService.getTransaction(container);
etc....
}
Complexity: Medium
> Portlet Application deployment integration with 2.7 deployment.
> ---------------------------------------------------------------
>
> Key: JBPORTAL-1906
> URL: http://jira.jboss.com/jira/browse/JBPORTAL-1906
> Project: JBoss Portal
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Julien Viet
> Fix For: 2.7 Final
>
>
> It covers:
> - Use JBoss Portal 2.7 deployment life cycle callbacks to manage the life cycle of PC 2.0 containers.
> - Integrate jboss-portlet.xml using a way that needs TBD (either separate or using the InfoFactory stuff), InfoFactory stuff is for now disabled but should be somehow reactived.
> - Ugly APIFactory was removed so remove JBossPortletRequest / JBossPortletResponse. We should use the new 2.0 features to handle those uses cases (like sign out).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list