[ https://issues.apache.org/jira/browse/TRINIDAD-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020197#comment-13020197 ]
Daniel Niklas commented on TRINIDAD-1910: ----------------------------------------- Hi Scott, i'm not a fan of workarounds, too! On the other side we needed a lot of patches and workarounds to get trinidad working within a poral (ie. PPR). And we have a lot of crucial applications working since 2008! We are very interested in better "trinidad-support" for portal environment! Perhaps it might be mor useful to consider which versions we could improve. We are planning to migrate to JSF2.0/Portlet2.0. I think here are much more possibilties to improve something like this. What ist the current status of 2.0-APIs and a portal bridge?! A configurable interim solution might be useful, too. > 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