June 2014 - gatein-issues - Jboss List Archives

[JBoss JIRA] (GTNPORTAL-3487) Add an option to load CSS from a CDN

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3487?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-3487: ---------------------------------------------------- Peter Palaga <ppalaga(a)redhat.com> changed the Status of [bug 1103765|https://bugzilla.redhat.com/show_bug.cgi?id=1103765] from ASSIGNED to MODIFIED > Add an option to load CSS from a CDN > ------------------------------------ > > Key: GTNPORTAL-3487 > URL: https://issues.jboss.org/browse/GTNPORTAL-3487 > Project: GateIn Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Peter Palaga > Assignee: Peter Palaga > Fix For: 3.8.2.Final, 3.9.0.Final > > > Loading CSS from an external URL is not possible ATM. This a task similar to GTNPORTAL-3485. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3487) Add an option to load CSS from a CDN

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3487?page=com.atlassian.jira.pl... ] RH Bugzilla Integration updated GTNPORTAL-3487: ----------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1103765 > Add an option to load CSS from a CDN > ------------------------------------ > > Key: GTNPORTAL-3487 > URL: https://issues.jboss.org/browse/GTNPORTAL-3487 > Project: GateIn Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Peter Palaga > Assignee: Peter Palaga > Fix For: 3.8.2.Final, 3.9.0.Final > > > Loading CSS from an external URL is not possible ATM. This a task similar to GTNPORTAL-3485. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3485) Add an option to load AMD JavaScript from a CDN

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3485?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-3485: ---------------------------------------------------- Peter Palaga <ppalaga(a)redhat.com> changed the Status of [bug 1103762|https://bugzilla.redhat.com/show_bug.cgi?id=1103762] from ASSIGNED to MODIFIED > Add an option to load AMD JavaScript from a CDN > ----------------------------------------------- > > Key: GTNPORTAL-3485 > URL: https://issues.jboss.org/browse/GTNPORTAL-3485 > Project: GateIn Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Peter Palaga > Assignee: Peter Palaga > Fix For: 3.8.2.Final, 3.9.0.Final > > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3485) Add an option to load AMD JavaScript from a CDN

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3485?page=com.atlassian.jira.pl... ] RH Bugzilla Integration updated GTNPORTAL-3485: ----------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1103762 > Add an option to load AMD JavaScript from a CDN > ----------------------------------------------- > > Key: GTNPORTAL-3485 > URL: https://issues.jboss.org/browse/GTNPORTAL-3485 > Project: GateIn Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Peter Palaga > Assignee: Peter Palaga > Fix For: 3.8.2.Final, 3.9.0.Final > > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3487) Add an option to load CSS from a CDN

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3487?page=com.atlassian.jira.pl... ] Peter Palaga updated GTNPORTAL-3487: ------------------------------------ Status: Resolved (was: Pull Request Sent) Fix Version/s: 3.8.2.Final 3.9.0.Final Resolution: Done > Add an option to load CSS from a CDN > ------------------------------------ > > Key: GTNPORTAL-3487 > URL: https://issues.jboss.org/browse/GTNPORTAL-3487 > Project: GateIn Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Peter Palaga > Assignee: Peter Palaga > Fix For: 3.8.2.Final, 3.9.0.Final > > > Loading CSS from an external URL is not possible ATM. This a task similar to GTNPORTAL-3485. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3502) Commnon deployer for JavaScript and skin services

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3502?page=com.atlassian.jira.pl... ] Peter Palaga updated GTNPORTAL-3502: ------------------------------------ Status: Resolved (was: Pull Request Sent) Fix Version/s: 3.8.2.Final 3.9.0.Final Resolution: Done > Commnon deployer for JavaScript and skin services > ------------------------------------------------- > > Key: GTNPORTAL-3502 > URL: https://issues.jboss.org/browse/GTNPORTAL-3502 > Project: GateIn Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Peter Palaga > Assignee: Peter Palaga > Fix For: 3.8.2.Final, 3.9.0.Final > > > At present, there are two independent deployers for JavaScript and skin services: {{GateInSkinConfigDeployer}} and {{JavascriptConfigDeployer}}. There are two problems with that: > (1) Both of them parse {{gatein-resources.xml}} independently, which is a performance drawback. > (2) They can succeed or fail independently, e.g. in case there is some meaningless declaration in {{gatein-resources.xml}}, which can lead to an inconsistent state of the portal. > An ideal solution for (2) would be to rollback deployment of the whole web application, but unfortunately, the present design of the portal does not allow for that. Therefore, I propose to keep at least the two services consistent by introducing a common deployer, that will grant that resources will either succeed to be added to both or to none. Problem (1) will be solved by that too. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3501) Introduce XML schema validation for gatein-resources.xml

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3501?page=com.atlassian.jira.pl... ] Peter Palaga updated GTNPORTAL-3501: ------------------------------------ Status: Resolved (was: Pull Request Sent) Fix Version/s: 3.8.2.Final 3.9.0.Final Resolution: Done > Introduce XML schema validation for gatein-resources.xml > -------------------------------------------------------- > > Key: GTNPORTAL-3501 > URL: https://issues.jboss.org/browse/GTNPORTAL-3501 > Project: GateIn Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Peter Palaga > Assignee: Peter Palaga > Fix For: 3.8.2.Final, 3.9.0.Final > > > There are several lines of code that indicate that {{org.exoplatform.commons.xml.XMLValidator}} was originally designed to check if a given document complies with an XML schema declared in it: > {code:java} > factory.setAttribute("http://java.sun.com/xml/jaxp/properties/schemaLanguage", "http://www.w3.org/2001/XMLSchema"); factory.setAttribute("http://java.sun.com/xml/jaxp/properties/schemaSource", schemas); > factory.setNamespaceAware(true); > factory.setValidating(true); > {code} > However, there were no tests checking if the validation works and indeed, it does not. It is out of the present scope to investigate what is wrong with {{XMLValidator}} and how it can be corrected, because it is too general to be used for validating {{gatein-resources.xml}} at this point. The main problem is that if we have not validated so far, there must be a lot of schema-incompatible {{gatein-resources.xml}} out there in the wild that were silently accepted by the portal in the past. Therefore, we cannot start validating all {{gatein-resources.xml}} files now. > To meet the natural expectation that inputs are properly validated to widest possible extent, I propose to start validating now, but only {{gatein-resources.xml}} documents that use the namespace {{http://www.gatein.org/xml/ns/gatein_resources_1_5}} or newer. {{gatein_resources_1_5.xsd}} will be introduced these days with fixing > GTNPORTAL-3485 and GTNPORTAL-3487. In this way we can stay backwards-compatible and start validating from now on. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3487) Add an option to load CSS from a CDN

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3487?page=com.atlassian.jira.pl... ] Peter Palaga updated GTNPORTAL-3487: ------------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/gatein/gatein-portal/pull/863 > Add an option to load CSS from a CDN > ------------------------------------ > > Key: GTNPORTAL-3487 > URL: https://issues.jboss.org/browse/GTNPORTAL-3487 > Project: GateIn Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Peter Palaga > Assignee: Peter Palaga > > Loading CSS from an external URL is not possible ATM. This a task similar to GTNPORTAL-3485. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3485) Add an option to load AMD JavaScript from a CDN

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3485?page=com.atlassian.jira.pl... ] Peter Palaga updated GTNPORTAL-3485: ------------------------------------ Status: Resolved (was: Pull Request Sent) Fix Version/s: 3.8.2.Final 3.9.0.Final Resolution: Done > Add an option to load AMD JavaScript from a CDN > ----------------------------------------------- > > Key: GTNPORTAL-3485 > URL: https://issues.jboss.org/browse/GTNPORTAL-3485 > Project: GateIn Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Peter Palaga > Assignee: Peter Palaga > Fix For: 3.8.2.Final, 3.9.0.Final > > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3501) Introduce XML schema validation for gatein-resources.xml

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3501?page=com.atlassian.jira.pl... ] Peter Palaga updated GTNPORTAL-3501: ------------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/gatein/gatein-portal/pull/863 > Introduce XML schema validation for gatein-resources.xml > -------------------------------------------------------- > > Key: GTNPORTAL-3501 > URL: https://issues.jboss.org/browse/GTNPORTAL-3501 > Project: GateIn Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Peter Palaga > Assignee: Peter Palaga > > There are several lines of code that indicate that {{org.exoplatform.commons.xml.XMLValidator}} was originally designed to check if a given document complies with an XML schema declared in it: > {code:java} > factory.setAttribute("http://java.sun.com/xml/jaxp/properties/schemaLanguage", "http://www.w3.org/2001/XMLSchema"); factory.setAttribute("http://java.sun.com/xml/jaxp/properties/schemaSource", schemas); > factory.setNamespaceAware(true); > factory.setValidating(true); > {code} > However, there were no tests checking if the validation works and indeed, it does not. It is out of the present scope to investigate what is wrong with {{XMLValidator}} and how it can be corrected, because it is too general to be used for validating {{gatein-resources.xml}} at this point. The main problem is that if we have not validated so far, there must be a lot of schema-incompatible {{gatein-resources.xml}} out there in the wild that were silently accepted by the portal in the past. Therefore, we cannot start validating all {{gatein-resources.xml}} files now. > To meet the natural expectation that inputs are properly validated to widest possible extent, I propose to start validating now, but only {{gatein-resources.xml}} documents that use the namespace {{http://www.gatein.org/xml/ns/gatein_resources_1_5}} or newer. {{gatein_resources_1_5.xsd}} will be introduced these days with fixing > GTNPORTAL-3485 and GTNPORTAL-3487. In this way we can stay backwards-compatible and start validating from now on. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues June 2014