[
https://issues.apache.org/jira/browse/TRINIDAD-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12670128#action_12670128
]
Scott O'Bryan commented on TRINIDAD-1383:
-----------------------------------------
Looking at this a bit closer, this patch severs a requirement we have in
trinidad where the Portlet Bridge classes should be optional on the classpath.
Our choices here are to use reflection or keep the logic in the PortletUtils
class where it was before. I'm going to re-apply your patch to the
PortletUtils class and keep that around. This way we won't have to worry about
running correctly when the bridge jars are not present.
> Update to support latest changes in portlet-bridge.
> ---------------------------------------------------
>
> Key: TRINIDAD-1383
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1383
> Project: MyFaces Trinidad
> Issue Type: Improvement
> Components: Portlet
> Affects Versions: 1.2.11-core
> Reporter: Felix Röthenbacher
> Assignee: Scott O'Bryan
> Attachments: TRINIDAD-1383-diff.txt
>
>
> Modifications in the portlet-bridge implementation post 1.0.0-beta require a
> change how a PortletNamingContainerUIViewRoot is constructed. This patch
> refactors the creation of a PortletNamingContainerUIViewRoot when running in
> a portlet environment. The modifications are backwards compatible to
> portlet-bridge versions 1.0.0-alpha and 1.0.0-beta. The modifications makes
> the PortletUtils class obsolete.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
