[ https://issues.apache.org/jira/browse/TRINIDAD-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020012#comment-13020012 ]
Scott O'Bryan commented on TRINIDAD-1910: ----------------------------------------- Hey Daniel, maybe as a compromise we can make this interim solution configurable. I'm not generally a big fan of this mind you, but the other solution is a lot harder and there hasn't been much movement on it. I will say that the real solution has finally found its way on my work docket, but I certainly don't have an ETA yet on this and you're right, it's taken a long time. We might be able to come up with something in sandbox or make it configurable whereby you can use a single non-namespaced javascript or multiple namespaced ones. I do not want to make this the default though. What do you think about that? > 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