[JBoss JIRA] Created: (GTNPORTAL-1720) Rename the confusing methods setFullRender/getFullRender in PortalRequestHandler
by Minh Hoang TO (JIRA)
Rename the confusing methods setFullRender/getFullRender in PortalRequestHandler
---------------------------------------------------------------------------------
Key: GTNPORTAL-1720
URL: https://jira.jboss.org/browse/GTNPORTAL-1720
Project: GateIn Portal
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Minh Hoang TO
{code:java}
/**
* Sets a boolean value to force whether portal will be fully rendered
* and it is only effective to an Ajax request.<p/>
*
* if the value is set to <code>true</code>, it means :<br/>
*
* 1) Only portal ui components are rendered <br/>
* 2) Portlets will be fully rendered if are inner of the portal ui components being updated
*
* @param forceFullUpdate
*/
final public void setFullRender(boolean forceFullUpdate)
{
this.forceFullUpdate = forceFullUpdate;
}
{code}
As mentioned in the Javadoc, while AJAX update is used, the forceFullUpdate decide whether only component of portal (ie: The components outside portlet window UIPortlet such as UIMaskWorkspace, UIWorkingWorkspace,...)
The name of method is very confusing. If we wish to update only components of portal, we have to call setFullRender(true) (I'm sure that most developers think of setFullRender(false) )
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] Created: (GTNPORTAL-1972) Gadgets don't work under loadbalancing
by kien nguyen (JIRA)
Gadgets don't work under loadbalancing
--------------------------------------
Key: GTNPORTAL-1972
URL: https://issues.jboss.org/browse/GTNPORTAL-1972
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: kien nguyen
Assignee: kien nguyen
Gadgets don't work under loadbalancing well, it looks as hosts routing (by balancer) prevents a gadget from getting of a right security token. Sticky sessions don't help with the problem
Solution we will add a system variable for path token key and when we setup GateIn cluster, you need to point this variable to this shared key, such as:
gatein.gadgets.securityTokenKeyFile=${gatein.conf.dir}/gadgets/key.txt
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] Created: (GTNPORTAL-1964) Improve Javascript lazy loading machanism
by Vu Viet Phuong (JIRA)
Improve Javascript lazy loading machanism
-----------------------------------------
Key: GTNPORTAL-1964
URL: https://issues.jboss.org/browse/GTNPORTAL-1964
Project: GateIn Portal
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Affects Versions: 3.2.0-M01
Reporter: Vu Viet Phuong
Currently we use eXo.require() function in eXo.js to make JS lazy loading request, this function make ajax request and use eval() function to execute the loaded JS, this is not good style in javascript
We should modify eXo.require() function (this should be transparent to user) to use JS lazy loading machanism defined in GATEIN/web/eXoResources/src/main/webapp/javascript/eXo/core/Loader.js
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] Created: (GTNPORTAL-1958) IFrame redirects to GateIn blog
by Marek Posolda (JIRA)
IFrame redirects to GateIn blog
-------------------------------
Key: GTNPORTAL-1958
URL: https://issues.jboss.org/browse/GTNPORTAL-1958
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 3.2.0-M01
Environment: GateIn 3.2.0-M1 with JBoss 5
Reporter: Marek Posolda
Fix For: 3.2.0-M02
- Login as root
- Add IFrame portlet to GateIn home page
- After refresh the page, browser redirects from GateIn portal to page http://community.jboss.org/en/gatein?view=blog
It seems that only some pages like blog are causing issue. Other pages like www.gatein.org are working fine with IFramePortlet. Simplest workaround can be to use different page than GateIn blog as default page for IFrame portlet. Better will be to change IFramePortlet to work correctly with all pages and handle redirects and other potential problems.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month