[jira] [Commented] (TRINIDAD-1910) portal: common.js is included serveral times
[ https://issues.apache.org/jira/browse/TRINIDAD-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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
[jira] [Commented] (TRINIDAD-1910) portal: common.js is included serveral times
[ https://issues.apache.org/jira/browse/TRINIDAD-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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
[jira] [Commented] (TRINIDAD-1910) portal: common.js is included serveral times
[ https://issues.apache.org/jira/browse/TRINIDAD-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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
Re: [jira] [Commented] (TRINIDAD-1910) portal: common.js is included serveral times
Sent from my iPhone On Apr 14, 2011, at 11:29 PM, Daniel Niklas (JIRA) dev@myfaces.apache.org wrote: [ https://issues.apache.org/jira/browse/TRINIDAD-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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
[jira] [Commented] (TRINIDAD-1910) portal: common.js is included serveral times
[ https://issues.apache.org/jira/browse/TRINIDAD-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13019236#comment-13019236 ] Daniel Niklas commented on TRINIDAD-1910: - TRINIDAD-53 - last activity 12/Jun/07 TRINIDAD-1705 - last activity 03/Feb/10 We are working in portal environment - we need a lot of patches and workarounds for Trinidad! Without this stop gap we are not able to use Trinidad for our productive applications! There seems to be no progress since years. 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
[jira] [Commented] (TRINIDAD-1910) portal: common.js is included serveral times
[ https://issues.apache.org/jira/browse/TRINIDAD-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13019416#comment-13019416 ] Scott O'Bryan commented on TRINIDAD-1910: - Daniel, I'm well aware but I'm not too enthused about putting in an incorrect solution either. Would you be interested in trying to work on the other trinidad solutions? Scott 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
[jira] [Commented] (TRINIDAD-1910) portal: common.js is included serveral times
[
https://issues.apache.org/jira/browse/TRINIDAD-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13018964#comment-13018964
]
Scott O'Bryan commented on TRINIDAD-1910:
-
Yes. This is a stop gap and, IMO, the wrong solution. The correct solution
would be to actually fix TRINIDAD-53. The Javascript obfuscator could be
modified to produce a set of tokenized JS libraries that contain something
like ${NAMESPACE} inside of them and then, before they are sent to the browser,
the ${NAMESPACE} token can be replaced with the portlet namespace. This will
mean you have multiple copies of the JS, but it would have version isolation.
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
[jira] Commented: (TRINIDAD-1910) portal: common.js is included serveral times
[ https://issues.apache.org/jira/browse/TRINIDAD-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12910774#action_12910774 ] Scott O'Bryan commented on TRINIDAD-1910: - Yeah, at most this is a stop gap.. What really needs to happen here is either: 1. namespacing of the trinidad javascripts (which there is another JIRA ticket for) or 2. proving some sort of javascipt versioning with a JS loader. The first would provide version isolation when portlets are inlined, the second is a lot harder but would provide us a single library being loaded per version. I'm not sure what the right solution would be,. 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: 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. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TRINIDAD-1910) portal: common.js is included serveral times
[ https://issues.apache.org/jira/browse/TRINIDAD-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12909200#action_12909200 ] Daniel Niklas commented on TRINIDAD-1910: - one more comment: this patch only works for portlets using the dame trinidad version! 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: 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. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TRINIDAD-1910) portal: common.js is included serveral times
[ https://issues.apache.org/jira/browse/TRINIDAD-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12908053#action_12908053 ] Daniel Niklas commented on TRINIDAD-1910: - Keep TRINIDAD-53 and TRINIDAD-1705 in mind, this would work, too. The solution for this issues is probably a lot of work... 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 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. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TRINIDAD-1910) portal: common.js is included serveral times
[ https://issues.apache.org/jira/browse/TRINIDAD-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12908056#action_12908056 ] Daniel Niklas commented on TRINIDAD-1910: - One comment to my patch: I could not find constants for adf/jsfLibs; Configuration seems to be outdated?! 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: 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. - You can reply to this email to add a comment to the issue online.
