[ https://issues.jboss.org/browse/GTNPORTAL-2347?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-2347: ---------------------------------------------------- Jared MORGAN <jmorgan(a)redhat.com&gt; made a comment on [bug 794463|https://bugzilla.redhat.com/show_bug.cgi?id=794463] Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,7 +1 @@ -Cause: We were missing a location to check for resourceIds when setting the resourceID for the portlet invocation. +It was discovered that ResourceIDs were sometimes lost when serving portlet resources because there was no way to check for resourceIds when setting the resourceID for the portlet invocation. The resourceIds would sometimes be null, resulting in resources not being properly fetched. The fix implements logic changes that now additionally check the Portal ResourceContext for resourceIDs. Resources now function more reliably, particularly when using the portlet bridge over WSRP.- -Consequence: The resourceIds would sometimes be null, resulting in resources not being properly fetched. - -Fix: also check the Portal ResourceContext for resourceIDs - -Result: resources work much better, especially when using the portlet bridge over wsrp. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/GTNPORTAL-2347?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-2347: ---------------------------------------------------- Matt Wringe <mwringe(a)redhat.com&gt; made a comment on [bug 794463|https://bugzilla.redhat.com/show_bug.cgi?id=794463] Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -It was discovered that ResourceIDs were sometimes lost when serving portlet resources because there was no way to check for resourceIds when setting the resourceID for the portlet invocation. The resourceIds would sometimes be null, resulting in resources not being properly fetched. The fix implements logic changes that now additionally check the Portal ResourceContext for resourceIDs. Resources now function more reliably, particularly when using the portlet bridge over WSRP.+It was discovered that ResourceIDs were sometimes lost when serving resources during a portlet invocation. The would cause the resourceIds to be null, resulting in resources not being properly fetched. The fix implements logic changes that now provide additional checks within the portal for resourceIDs. Resources now function more reliably, particularly when using the portlet bridge over WSRP. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/GTNPORTAL-2347?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-2347: ---------------------------------------------------- Jared MORGAN <jmorgan(a)redhat.com&gt; made a comment on [bug 794463|https://bugzilla.redhat.com/show_bug.cgi?id=794463] Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -It was discovered that ResourceIDs were sometimes lost when serving resources during a portlet invocation. The would cause the resourceIds to be null, resulting in resources not being properly fetched. The fix implements logic changes that now provide additional checks within the portal for resourceIDs. Resources now function more reliably, particularly when using the portlet bridge over WSRP.+It was discovered that ResourceIDs were sometimes lost when serving resources during a portlet invocation. This would cause the resourceIds to be null, resulting in resources not being properly fetched. The fix implements logic changes that now provide additional checks within the portal for resourceIDs. Resources now function more reliably, particularly when using the portlet bridge over WSRP. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira