[JBoss JIRA] (GTNPORTAL-2581) RichFaces is not defined after adding a RF portlet to a page
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2581?page=com.atlassian.jira.pl... ]
RH Bugzilla Integration commented on GTNPORTAL-2581:
----------------------------------------------------
Honza Fnukal <hfnukal(a)redhat.com> changed the Status of [bug 1080249|https://bugzilla.redhat.com/show_bug.cgi?id=1080249] from MODIFIED to ON_QA
> RichFaces is not defined after adding a RF portlet to a page
> ------------------------------------------------------------
>
> Key: GTNPORTAL-2581
> URL: https://issues.jboss.org/browse/GTNPORTAL-2581
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Environment: GateIn 3.4.0.Final
> Reporter: Peter Palaga
> Attachments: jsf2-rf4-hello-world-portlet.war
>
>
> (1) Start a fresh GateIn 3.4.0.Final:
> cd tmp
> wget http://downloads.jboss.org/gatein/Releases/Portal/3.4.0.Final/GateIn-3.4....
> unzip GateIn-3.4.0.Final-jbossas7.zip
> cd GateIn-3.4.0.Final-jbossas7/bin
> ./standalone.sh
> (2) Install gatein-bom-3.4
> git clone https://github.com/ppalaga/gatein-bom.github
> cd gatein-bom
> mvn install -Dgpg.skip=true
> (3) Pack and deploy jsf2-rf4-hello-world-portlet:
> cd tmp
> git clone https://github.com/ppalaga/gatein-portal-quickstart.git
> cd gatein-portal-quickstart/jsf2-rf4-hello-world-portlet
> mvn package jboss-as:deploy
> (4) In web browser:
> * login as root http://127.0.0.1:8080/portal/login?username=root&password=gtn&initialURI=...
> (5) In web browser:
> * Group > Administration > Application Registry > Import Applications
> * Site > Classic > Home
> * Site Editor > Edit Page
> * Drag jsf2-rf4-hello-world-portlet and drop it e.g. under the Home Page portlet
> * make the console with server log visible to you
> * Open developer tools (F12 in Chrome) and switch to Resources. Have a look at loaded scripts. Note that there are no PBR-related scripts there.
> (6) Hit Finish (Diskette Icon) in Page Editor dialog
> (7) UNEXPECTED: After hitting Finish, there comes a modal message in the browser window saying "RichFaces is not defined".
> * Note that while this message is being displayed, there is no change in the scripts compared to before (5).
> * Note that nothing happened in the server log.
>
> (8) Hit OK in the "RichFaces is not defined" alert.
> * Note that one or more PBR-related scripts were loaded. Some of them have error markers in them
> * Sometimes one or more org.exoplatform.portal.config.NoSuchDataExceptions appear in the server log
>
> The problem seems to be related to the fact that the inline JavaScript needed to render the rich:select component is evaluated before the needed js resources were loaded. After reloading the whole page or accessing the page from another session jsf2-rf4-hello-world-portlet works as expected.
> For further observations, define one more step:
> (9)
> * Site > Classic > Home
> * Site Editor > Edit Page
> * remove jsf2-rf4-hello-world-portlet from the page
> * Hit Finish (Diskette Icon) in Page Editor dialog
> When in the state after (8), one performs (9) and then again (5) and (6), "RichFaces is not defined" does not appear.
> "RichFaces is not defined" appears only when one signs out from the portal and signs in again between (9) and (5) of the previous scenario.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 5 months
[JBoss JIRA] (GTNPORTAL-3502) Commnon deployer for JavaScript and skin services
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3502?page=com.atlassian.jira.pl... ]
RH Bugzilla Integration commented on GTNPORTAL-3502:
----------------------------------------------------
Honza Fnukal <hfnukal(a)redhat.com> changed the Status of [bug 1103768|https://bugzilla.redhat.com/show_bug.cgi?id=1103768] from MODIFIED to ON_QA
> 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)
10 years, 5 months
[JBoss JIRA] (GTNPORTAL-3110) IDM DAO classes are only catching IdentityExceptions
by Boubaker Khanfir (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3110?page=com.atlassian.jira.pl... ]
Boubaker Khanfir commented on GTNPORTAL-3110:
---------------------------------------------
I think that we have a regression here. Any exception from IDM operations will cause a rollback without throwing an exception. That's what was fixed here:
GTNPORTAL-3243
IMO, we have to throw an exception at the end of "recoverFromIDMError" method.
Should I open a new issue for that ?
Fix Version should be for 3.5+
> IDM DAO classes are only catching IdentityExceptions
> ----------------------------------------------------
>
> Key: GTNPORTAL-3110
> URL: https://issues.jboss.org/browse/GTNPORTAL-3110
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Identity integration
> Affects Versions: 3.6.0.Beta02
> Reporter: Martin Weiler
> Assignee: Marek Posolda
> Fix For: 3.6.0.Final
>
>
> In some IDM DAO classes, such as GroupDAOImpl, MembershipDAOImpl and UserProfileDAOImpl all IDM calls are wrapped with try..catch(Exception e) blocks, which ensures that not only IdentityException, but also Hibernate exceptions are caught and recovered with rollback().
> But in UserDAOImpl only "IdentityException e" instances are caught. So HibernateException are not handled, which can result in transaction errors. Additionally, in MembershipTypeDAOImpl the IDM calls are not wrapped with any catch blocks, which also needs to be fixed.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 5 months
[JBoss JIRA] (GTNPORTAL-3509) [Application Registry] Missing validator when importing applications
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3509?page=com.atlassian.jira.pl... ]
RH Bugzilla Integration commented on GTNPORTAL-3509:
----------------------------------------------------
Lucas Ponce <lponce(a)redhat.com> changed the Status of [bug 1107566|https://bugzilla.redhat.com/show_bug.cgi?id=1107566] from NEW to POST
> [Application Registry] Missing validator when importing applications
> --------------------------------------------------------------------
>
> Key: GTNPORTAL-3509
> URL: https://issues.jboss.org/browse/GTNPORTAL-3509
> Project: GateIn Portal
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Affects Versions: 3.5.10.Final, 3.7.1.Final, 3.8.2.Final
> Reporter: H. Trang Vu
> Assignee: Lucas Ponce
> Priority: Minor
> Attachments: SiteRedirectsAndImportExportAdminPortlet-TooLongAppName-DisplayName.png
>
>
> When applications are added by configuration or by importing automatically all applications, there isn't any check of application name while its value is read-only after the creation. These validators (length and pattern) however existent when adding or editing an application. As a consequence, some imported applications cannot be changed (Display Name, Description, Access Permission).
> Steps to reproduce:
> # Login as root
> # Go to Application Registry
> # Click *Site Redirects and Import/Export* (the last item of *Administration* category).
> # Change nothing. Click Save. Warning message appears as follows.
> {noformat}
> The length of the text in field "Application Name" must be between "3" and "30" characters.
> The length of the text in field "Display Name" must be between "3" and "30" characters.
> {noformat}
> * It is feasible to reduce "Display Name" but not "Application Name" at run time.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 5 months
[JBoss JIRA] (GTNPORTAL-3509) [Application Registry] Missing validator when importing applications
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3509?page=com.atlassian.jira.pl... ]
RH Bugzilla Integration updated GTNPORTAL-3509:
-----------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1107566
> [Application Registry] Missing validator when importing applications
> --------------------------------------------------------------------
>
> Key: GTNPORTAL-3509
> URL: https://issues.jboss.org/browse/GTNPORTAL-3509
> Project: GateIn Portal
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Affects Versions: 3.5.10.Final, 3.7.1.Final, 3.8.2.Final
> Reporter: H. Trang Vu
> Assignee: Lucas Ponce
> Priority: Minor
> Attachments: SiteRedirectsAndImportExportAdminPortlet-TooLongAppName-DisplayName.png
>
>
> When applications are added by configuration or by importing automatically all applications, there isn't any check of application name while its value is read-only after the creation. These validators (length and pattern) however existent when adding or editing an application. As a consequence, some imported applications cannot be changed (Display Name, Description, Access Permission).
> Steps to reproduce:
> # Login as root
> # Go to Application Registry
> # Click *Site Redirects and Import/Export* (the last item of *Administration* category).
> # Change nothing. Click Save. Warning message appears as follows.
> {noformat}
> The length of the text in field "Application Name" must be between "3" and "30" characters.
> The length of the text in field "Display Name" must be between "3" and "30" characters.
> {noformat}
> * It is feasible to reduce "Display Name" but not "Application Name" at run time.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 5 months
[JBoss JIRA] (GTNPORTAL-3499) Result of Rest API contains original host when Gatein runs behind apache server via HTTP protocol
by Tuyen Nguyen The (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3499?page=com.atlassian.jira.pl... ]
Tuyen Nguyen The resolved GTNPORTAL-3499.
-----------------------------------------
Resolution: Won't Fix
> Result of Rest API contains original host when Gatein runs behind apache server via HTTP protocol
> -------------------------------------------------------------------------------------------------
>
> Key: GTNPORTAL-3499
> URL: https://issues.jboss.org/browse/GTNPORTAL-3499
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.5.9.Final
> Reporter: Tran Trung Thanh
> Assignee: Tuyen Nguyen The
> Original Estimate: 6 hours
> Time Spent: 2 hours
> Remaining Estimate: 0 minutes
>
> - Configure eXo Platform with apache 2 via HTTP protocol by following
> http://docs.exoplatform.com/public/topic/PLF40/PLFAdminGuide.Deployment.S...
> - Start Gatein server at localhost:8080
> - Access Gatein service by using address of apache for example example.localhost
> - Login as john
> - Call REST API: http://example.localhost/rest/private/managed-components/mop/usersites/jo...
> -> The result contains the original host
> {noformat}
> {"description":"List of child pages for page 'Tab_Default'","children":[],"operations":[{"operation-name":"read-resource","operation-description":"Lists available pages at a specified address.","link":{"rel":"self","href":"http://localhost:8080/rest/private/managed-components/mop/usersites/john/..."}},{"operation-name":"read-config-as-xml","operation-description":"Reads pages as configuration xml at a specified address.","link":{"rel":"content","href":"http://localhost:8080/rest/private/managed-components/mop/usersites/john/...","type":"application/xml"}},{"operation-name":"export-resource","operation-description":"Exports pages configuration xml as a zip file.","link":{"rel":"content","href":"http://localhost:8080/rest/private/managed-components/mop/usersites/john/...","type":"application/zip","method":"get"}}]}
> {noformat}
> Note that: No problem when configuring apache front-end with ajp.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 5 months