[
https://issues.apache.org/jira/browse/TRINIDAD-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020201#comment-13020201
]
Scott O'Bryan commented on TRINIDAD-1910:
-----------------------------------------
Well, Trinidad is tested as part of the portlet bridge TCK (obviously NOT with
more then one portlet). The portlet bridge 3.0 just had it's first alpha
release and, although it mostly passes the JSR-328 TCK, the ppr stuff in
Trinidad fails. We did have some Trinidad issues but those were fixed and now
t looks like the remaining issues are on the bridge side.
As for the state of the JSR, right now it hasn't really been kicked off yet.
The myFaces Portlet bridge 3.0 will support the 328 TCK, but with JSF 2.0. So
while I don't expect an official bridge with accompanying JSR any time soon, I
think you will see Trinidad support for the portlet bridge 3.0 evolve fairly
quickly.
Might be prudent to continue this discussion on the user list.
> portal: common.js is included serveral times
> --------------------------------------------
>
> Key: TRINIDAD-1910
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1910
> Project: MyFaces Trinidad
> Issue Type: Bug
> Components: Portlet
> Affects Versions: 1.0.10-core
> Reporter: Daniel Niklas
> Attachments: Page.js-trinidad-1910-patch.txt, XhtmlUtils-patch.txt
>
>
> The commons.js is included several times, when you have more than one
> trinidad-porlet on your portal-site.
> In XhtmlUtils#writeLibImport there is a mechanism to prevent including
> javascript libs more than one time (portal environment). This mechanism is
> not working, when you have more than one Trinidad-portlets within different
> web apps.
> The problem is, that the key contains the webapp context!
> Here " _uixJSL" for example contains:
> "/webapp-one/adf/jsLibs/Common1_0_10.js"
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
