[JBoss JIRA] (GTNPORTAL-3451) Infinispan transport clusterName property not properly defined
by Peter Palaga (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3451?page=com.atlassian.jira.pl... ]
Peter Palaga updated GTNPORTAL-3451:
------------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 3.8.0.Final
Resolution: Done
> Infinispan transport clusterName property not properly defined
> --------------------------------------------------------------
>
> Key: GTNPORTAL-3451
> URL: https://issues.jboss.org/browse/GTNPORTAL-3451
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Lucas Ponce
> Assignee: Lucas Ponce
> Fix For: 3.8.0.Final
>
>
> clusterName attribute is not well defined for infinispan transport defined in HA configurations.
> This bug shows followings warnings:
> [...]
> 14:47:59,283 WARN [org.infinispan.util.StringPropertyReplacer] (MSC service thread 1-2) ISPN000003: Property infinispan-cluster-name could not be replaced as intended!
> [...]
> And this bug is root cause for other cascading errors in cluster setup.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (GTNPORTAL-3454) Remove native AMD modules from requireJs config
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3454?page=com.atlassian.jira.pl... ]
RH Bugzilla Integration commented on GTNPORTAL-3454:
----------------------------------------------------
Peter Palaga <ppalaga(a)redhat.com> changed the Status of [bug 1090470|https://bugzilla.redhat.com/show_bug.cgi?id=1090470] from ASSIGNED to POST
> Remove native AMD modules from requireJs config
> -----------------------------------------------
>
> Key: GTNPORTAL-3454
> URL: https://issues.jboss.org/browse/GTNPORTAL-3454
> Project: GateIn Portal
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Peter Palaga
> Assignee: Peter Palaga
> Fix For: 3.8.0.Final
>
>
> RequireJs config is a json structure renderead inline in the HTML markup of every page returned by the portal. The recent "Native AMD Support" feature has brought the possibility to work with large third-party javascript frameworks such as Dojo containing thousands of JavaScript modules. The present implementation adds an entry for every native AMD module into RequireJs config. With a dojo portlet deployed, this causes an overhead of more than 400KB per page.
> Steps to Reproduce:
> 1. Compile and deploy the dojo portlet application from https://github.com/ppalaga/dojo-portlet
> 2. Import applications
> 3. Inspect the source of any portal page, e.g. /portal/classic/home
> 4. Locate the line starting with
> var require =
> Actual results: All dojo resources are there in the json structure assigned to the require variable.
> Expected results: No resources coming from Dojo should be there.
> Additional info: Not having the resources coming from Dojo in requireJS config is technically possible as the native AMD modules are implicitly SHARED and the baseUrl is set properly in the config.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (GTNPORTAL-3454) Remove native AMD modules from requireJs config
by Peter Palaga (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3454?page=com.atlassian.jira.pl... ]
Peter Palaga updated GTNPORTAL-3454:
------------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 3.8.0.Final
Resolution: Done
> Remove native AMD modules from requireJs config
> -----------------------------------------------
>
> Key: GTNPORTAL-3454
> URL: https://issues.jboss.org/browse/GTNPORTAL-3454
> Project: GateIn Portal
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Peter Palaga
> Assignee: Peter Palaga
> Fix For: 3.8.0.Final
>
>
> RequireJs config is a json structure renderead inline in the HTML markup of every page returned by the portal. The recent "Native AMD Support" feature has brought the possibility to work with large third-party javascript frameworks such as Dojo containing thousands of JavaScript modules. The present implementation adds an entry for every native AMD module into RequireJs config. With a dojo portlet deployed, this causes an overhead of more than 400KB per page.
> Steps to Reproduce:
> 1. Compile and deploy the dojo portlet application from https://github.com/ppalaga/dojo-portlet
> 2. Import applications
> 3. Inspect the source of any portal page, e.g. /portal/classic/home
> 4. Locate the line starting with
> var require =
> Actual results: All dojo resources are there in the json structure assigned to the require variable.
> Expected results: No resources coming from Dojo should be there.
> Additional info: Not having the resources coming from Dojo in requireJS config is technically possible as the native AMD modules are implicitly SHARED and the baseUrl is set properly in the config.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months