August 2010 - gatein-issues - Jboss List Archives

[JBoss JIRA] Created: (GTNPORTAL-1383) UIPortletLifecycle does not call Portlet.render() if the window state is "minimized"

by Jörg Harm (JIRA)

UIPortletLifecycle does not call Portlet.render() if the window state is "minimized" ------------------------------------------------------------------------------------ Key: GTNPORTAL-1383 URL: https://jira.jboss.org/browse/GTNPORTAL-1383 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.1.0-GA Reporter: Jörg Harm UIPortletLifecycle does not call Portlet.render(RenderRequest,RenderResponse) if the window state is "minimized". The Portlet Spec says "When a portlet is in MINIMIZED window state, the portlet should only render minimal output or no output at all". Even minimal output is output and should not be ignored by the Portal. I did not find a hint in the Portlet Spec that a Portal implementation is allowed to omit the call to the render method in window state "minimized". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
9
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1372) the handling of Portlet Mode does not work correctly

by Trong Tran (JIRA)

the handling of Portlet Mode does not work correctly ---------------------------------------------------- Key: GTNPORTAL-1372 URL: https://jira.jboss.org/browse/GTNPORTAL-1372 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Common integration Affects Versions: 3.1.0-GA Reporter: Trong Tran Fix For: 3.2.0-GA In Edit mode of a portlet, I create a RenderURL and setPortletMode back to View mode like following : {code} PortletURL renderURL = res.createRenderURL(); renderURL.setPortletMode(PortletMode.VIEW); w.write("Click <a href=\"" + renderURL.toString() + "\">here</a> to switch to VIEW mode"); {code} Unfortunately it does not return to View mode after i click on the link. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1382) GateIn should use the portlet title set at RenderResponse in the portlet window bar

by Jörg Harm (JIRA)

GateIn should use the portlet title set at RenderResponse in the portlet window bar ----------------------------------------------------------------------------------- Key: GTNPORTAL-1382 URL: https://jira.jboss.org/browse/GTNPORTAL-1382 Project: GateIn Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: WebUI Affects Versions: 3.1.0-GA Reporter: Jörg Harm GateIn should use the portlet title set at RenderResponse in the portlet window bar to allow the developer to create dynamic portlet titles. This would automatically allow for i18n of the portlet title in the way recommended by the PortletSpec. Here is the way the title set at RenderResponse takes his way through GateIn: - org.gatein.pc.portlet.impl.jsr168.api.RenderResponseImpl.createMarkupResponse(...) creates an instance of org.gatein.pc.api.invocation.response.FragmentResponse passing the title to it - org.exoplatform.portal.webui.application.UIPortletLifecycle takes the title from the FragmentResponse in its method processRender(...) binding it to the key "portletTitle" in the org.exoplatform.webui.core.lifecycle.WebuiBindingContext before rendering the template of the org.exoplatform.portal.webui.application.UIPortlet - the template UIPortlet.gtmpl does not use the portletTitle UIPortletLifecycle takes "Portlet" as portletTitle if no title is set at the FragmentResponse. I think UIPortletLifecycle should better not bind any value at all to "portletTitle" in the WebuiBindingContext in this case instead of a hard-coded value. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

4
10
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-773) Ability to disable caching and adding debug on gadgets through the developping parameter

by Thomas Heute (JIRA)

Ability to disable caching and adding debug on gadgets through the developping parameter ---------------------------------------------------------------------------------------- Key: GTNPORTAL-773 URL: https://jira.jboss.org/jira/browse/GTNPORTAL-773 Project: GateIn Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Thomas Heute Fix For: 3.1.0 Debug and No cache used to be set on the UI, it has been removed. We need to reenable this if the exo.developping paramater is used -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1414) Document the GateIn object XSD

by Minh Hoang TO (JIRA)

Document the GateIn object XSD ------------------------------ Key: GTNPORTAL-1414 URL: https://jira.jboss.org/browse/GTNPORTAL-1414 Project: GateIn Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 3.1.0-GA Reporter: Minh Hoang TO Assignee: Minh Hoang TO Priority: Minor Fix For: 3.2.0-GA Gatein has an xml schema for pages.xml and navigation.xml But it is missing from the reference guide. Please add a paragraph about it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1309) GateIn LDAP usernames are not case sensitive

by Boleslaw Dawidowicz (JIRA)

GateIn LDAP usernames are not case sensitive -------------------------------------------- Key: GTNPORTAL-1309 URL: https://jira.jboss.org/browse/GTNPORTAL-1309 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Identity integration Affects Versions: 3.1.0-CR01 Reporter: Boleslaw Dawidowicz Assignee: Boleslaw Dawidowicz Fix For: 3.2.0-GA Quote from forums: "The problem seems to be case sensitivity on the username attribute. Our usernames are stored in uppercase: ABA so if i login as "ABA" with correct password it works. if i login as "aba" a new user is created and i get a 403 error page. Loggin in as admin i can now see 2 entries for user "ABA" - one in uppercase and one in lowercase." -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1351) User commons file upload for component.web module

by Julien Viet (JIRA)

User commons file upload for component.web module ------------------------------------------------- Key: GTNPORTAL-1351 URL: https://jira.jboss.org/browse/GTNPORTAL-1351 Project: GateIn Portal Issue Type: Task Security Level: Public (Everyone can see) Reporter: Julien Viet Assignee: Trong Tran Fix For: 3.2.0-GA -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-256) Replace the exopackage structure with maven tooling

by Dimitri BAELI (JIRA)

Replace the exopackage structure with maven tooling --------------------------------------------------- Key: GTNPORTAL-256 URL: https://jira.jboss.org/jira/browse/GTNPORTAL-256 Project: GateIn Portal Issue Type: Task Components: Packaging Reporter: Dimitri BAELI Assignee: Dimitri BAELI Fix For: 3.0.0-CR01 Current GateIn packaging is done using an exopackage tooling (scripting written in javascript). This tooling is hard to maintain and should be replaced by a more maintainable tooling (maven / java). EXPECTED: * Include the tooling in gate to ease its replacement by a more convenient tooling and avoid the need to update an external tool in GateIn dependencies * Then review the used functionalities and replace them by common maven features or a dedicated maven plugin TARGET: * All this code should be gone for Gate 3.0 GA -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (GTNPC-23) If no cache level is set by a portlet for a resource URL, it should default to the parent resource cache level or PAGE if there is none.

by Chris Laprun (JIRA)

If no cache level is set by a portlet for a resource URL, it should default to the parent resource cache level or PAGE if there is none. ---------------------------------------------------------------------------------------------------------------------------------------- Key: GTNPC-23 URL: https://jira.jboss.org/browse/GTNPC-23 Project: GateIn Portlet Container Issue Type: Bug Affects Versions: 2.1.1-GA Reporter: Chris Laprun Per the JSR 286 spec (PLT.13.7): If no cachability is set on the resource URL, the cacheability setting of the parent resource is used. If no parent resource is available, PAGE is the default. This doesn't seem to be currently the case in the code, where the cacheability setting stays null if setCacheability is not called on ResourceURL. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-854) Login Exception when input invalid password in Sign In form

by Hang Nguyen (JIRA)

Login Exception when input invalid password in Sign In form ----------------------------------------------------------- Key: GTNPORTAL-854 URL: https://jira.jboss.org/jira/browse/GTNPORTAL-854 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Security Reporter: Hang Nguyen Assignee: Julien Viet Fix For: 3.0.0-GA - Go to http://localhost:8080/portal/public/classic/ - Click Sign In form - Input user name: root - Input password: abc - Click Sign In - Return to form of private mode --> OK - Input valid pass: gtn - Click Sign In button => Can't login to portal and return to http://localhost:8080/portal/private/j_security_check. Show exception in cygwin: WARNING: Login exception authenticating username "null" javax.security.auth.login.LoginException at org.exoplatform.services.security.jaas.DefaultLoginModule.commit(DefaultLoginModule.java: 155) at org.exoplatform.services.security.j2ee.TomcatLoginModule.commit(TomcatLoginModule.java:47 ) at sun.reflect.GeneratedMethodAccessor343.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769) at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186) at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680) at javax.security.auth.login.LoginContext.login(LoginContext.java:580) at org.apache.catalina.realm.JAASRealm.authenticate(JAASRealm.java:363) at org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAuthenticator.java:2 58) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:417) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.ja va:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:619) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues August 2010