[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:
----------------------------------------------------
Honza Fnukal <hfnukal(a)redhat.com> changed the Status of [bug 1090470|https://bugzilla.redhat.com/show_bug.cgi?id=1090470] from MODIFIED to ON_QA
> 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 was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (GTNPORTAL-3469) PortalSetupCommand does not ensure that initialpassword is written on a new line
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3469?page=com.atlassian.jira.pl... ]
RH Bugzilla Integration commented on GTNPORTAL-3469:
----------------------------------------------------
Honza Fnukal <hfnukal(a)redhat.com> changed the Status of [bug 1094163|https://bugzilla.redhat.com/show_bug.cgi?id=1094163] from MODIFIED to ON_QA
> PortalSetupCommand does not ensure that initialpassword is written on a new line
> --------------------------------------------------------------------------------
>
> Key: GTNPORTAL-3469
> URL: https://issues.jboss.org/browse/GTNPORTAL-3469
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Peter Palaga
> Assignee: Peter Palaga
> Fix For: 3.8.0.Final
>
>
> Steps to reproduce:
> (1) Ensure that {{$JBOSS_HOME/standalone/configuration/gatein/configuration.properties}} do not contain gatein.portal.setup.initialpassword.root in any form: commented or active.
> (2) Ensure that the last key value pair is not terminated with a new line character
> (3) run {{$JBOSS_HOME/bin/portal-setup.sh" -p "secret"}}
> Not OK: The {{configuration.properties}} file ends with
> {code:plain}
> # Logged user keep alive
> gatein.webui.keepalive.enabled=true
> gatein.webui.keepalive.interval=60000gatein.portal.setup.initialpassword.root=6MSyXIj3kkQ= # Modified by portal-setup.sh
> {code}
> Expected:
> {code:plain}
> # Logged user keep alive
> gatein.webui.keepalive.enabled=true
> gatein.webui.keepalive.interval=60000
> gatein.portal.setup.initialpassword.root=6MSyXIj3kkQ= # Modified by portal-setup.sh
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months