July 2011 - gatein-issues - Jboss List Archives

[JBoss JIRA] Created: (GTNMAVEN-27) Update the third parties version in exopackage to compatible with JCR 1.14.0-CR1

by Khoi Nguyen (JIRA)

Update the third parties version in exopackage to compatible with JCR 1.14.0-CR1 --------------------------------------------------------------------------------- Key: GTNMAVEN-27 URL: https://issues.jboss.org/browse/GTNMAVEN-27 Project: GateIn Maven Issue Type: Task Reporter: Khoi Nguyen Update 2 third parties to new version: commons-pool:commons-pool 1.2 -> 1.5.5 commons-dbcp:commons-dbcp 1.2.1 -> 1.4 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1396) Allow to access gadget edit mode with wrapper portlet

by Patrice Lamarque (JIRA)

Allow to access gadget edit mode with wrapper portlet ----------------------------------------------------- Key: GTNPORTAL-1396 URL: https://jira.jboss.org/browse/GTNPORTAL-1396 Project: GateIn Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 3.1.0-GA Reporter: Patrice Lamarque The wrapper portlet does not let us access to the preferences of the gadget. Ideally this would be achieved by displaying the gadget preferences view on the portlet edit mode. This feature is set as major, because without it, the wrapper portlet is mostly useless for many configurable gadgets. -- 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, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1924) Can't redirect to the origin requested URL after login

by Vu Viet Phuong (JIRA)

Can't redirect to the origin requested URL after login ------------------------------------------------------ Key: GTNPORTAL-1924 URL: https://issues.jboss.org/browse/GTNPORTAL-1924 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.1.0-GA Environment: Ubuntu 11, Jetty 6.1.25 Reporter: Vu Viet Phuong - Go to http://localhost:8080/portal/private/classic/organization/management - Redirect to login page - Login with root --> redirect to HOME page ---> error Expected : redirect to the origin requested uri : http://localhost:8080/portal/private/classic/organization/management This bug can only be reproduced with Jetty server -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

4
10
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1963) Sprint 57 activities

by Minh Hoang TO (JIRA)

Sprint 57 activities -------------------- Key: GTNPORTAL-1963 URL: https://issues.jboss.org/browse/GTNPORTAL-1963 Project: GateIn Portal Issue Type: Task Security Level: Public (Everyone can see) Reporter: Minh Hoang TO -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1944) DateTimeValidator has superflous code that breaks localized date timestamps

by Matt Davis (JIRA)

DateTimeValidator has superflous code that breaks localized date timestamps --------------------------------------------------------------------------- Key: GTNPORTAL-1944 URL: https://issues.jboss.org/browse/GTNPORTAL-1944 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: WebUI Affects Versions: 3.1.0-GA Reporter: Matt Davis http://anonsvn.jboss.org/repos/gatein/epp/portal/tags/EPP_5_1_0_GA/webui/... has an additional check where the date input value needs to match the (not localized) DATETIME_REGEX, which is superfluous and causes localized date input to fail: Index: core/src/main/java/org/exoplatform/webui/form/validator/DateTimeValidator.java =================================================================== --- core/src/main/java/org/exoplatform/webui/form/validator/DateTimeValidator.java (revision 6667) +++ core/src/main/java/org/exoplatform/webui/form/validator/DateTimeValidator.java (working copy) @@ -43,17 +43,11 @@ public class DateTimeValidator implements Validator { - static private final String SPLIT_REGEX = "/|\\s+|:"; - - static private final String DATETIME_REGEX = - "^(\\d{1,2}\\/\\d{1,2}\\/\\d{1,4})\\s*(\\s+\\d{1,2}:\\d{1,2}:\\d{1,2})?$"; - public void validate(UIFormInput uiInput) throws Exception { if (uiInput.getValue() == null || ((String)uiInput.getValue()).trim().length() == 0) return; String s = (String)uiInput.getValue(); - DateFormat stFormat = new SimpleDateFormat("MM/dd/yyyy HH:mm:ss"); UIFormDateTimeInput uiDateInput = (UIFormDateTimeInput)uiInput; SimpleDateFormat sdf = new SimpleDateFormat(uiDateInput.getDatePattern_().trim()); @@ -79,24 +73,5 @@ { throw new MessageException(new ApplicationMessage("DateTimeValidator.msg.Invalid-input", args, ApplicationMessage.WARNING)); } - if (s.matches(DATETIME_REGEX) && isValidDateTime(s)) - return; - - throw new MessageException(new ApplicationMessage("DateTimeValidator.msg.Invalid-input", args, ApplicationMessage.WARNING)); } - - private boolean isValidDateTime(String dateTime) - { - String[] arr = dateTime.split(SPLIT_REGEX, 7); - int valid = Integer.parseInt(arr[0]); - if (valid < 1 || valid > 12) - return false; - Calendar date = new GregorianCalendar(Integer.parseInt(arr[2]), valid - 1, 1); - if (Integer.parseInt(arr[1]) > date.getActualMaximum(Calendar.DAY_OF_MONTH)) - return false; - if (arr.length > 3 - && (Integer.parseInt(arr[3]) > 23 || Integer.parseInt(arr[4]) > 59 || Integer.parseInt(arr[5]) > 59)) - return false; - return true; - } } -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

4
9
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1845) clustering sso, ws-security and login Improvements

by Matt Wringe (JIRA)

clustering sso, ws-security and login Improvements -------------------------------------------------- Key: GTNPORTAL-1845 URL: https://issues.jboss.org/browse/GTNPORTAL-1845 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Matt Wringe As discussed here: http://lists.jboss.org/pipermail/gatein-dev/2011-March/000923.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
1
0 / 0

[JBoss JIRA] Updated: (GTNPORTAL-1974) Add Node button always create new node on the top level

by Honza Fnukal (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-1974?page=com.atlassian.jira.pl... ] Honza Fnukal updated GTNPORTAL-1974: ------------------------------------ Assignee: (was: Honza Fnukal) > Add Node button always create new node on the top level > ------------------------------------------------------- > > Key: GTNPORTAL-1974 > URL: https://issues.jboss.org/browse/GTNPORTAL-1974 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Michal Vanco > Labels: EPP_5.1.x_Triage > > Using Add Node button in Navigation Management (Site or Group) always create new node at the top level. > When you have some subnode selected and Add Node button is used, node is created at the top level. > Only way to create subnode is to use context menu otherwise node selection is ignored. > Maybe it's wanted behavior, but IMO users would appreciate to create node on current selection. > Or is there reason for this behavior? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Moved: (GTNPORTAL-1974) Add Node button always create new node on the top level

by Honza Fnukal (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-1974?page=com.atlassian.jira.pl... ] Honza Fnukal moved JBEPP-1034 to GTNPORTAL-1974: ------------------------------------------------ Project: GateIn Portal (was: JBoss Enterprise Portal Platform) Key: GTNPORTAL-1974 (was: JBEPP-1034) Affects Version/s: (was: 5.1.0.CR01) (was: 5.1.1.DEV01) Fix Version/s: (was: 5.2.0.DEV02) > Add Node button always create new node on the top level > ------------------------------------------------------- > > Key: GTNPORTAL-1974 > URL: https://issues.jboss.org/browse/GTNPORTAL-1974 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Michal Vanco > Assignee: Honza Fnukal > Labels: EPP_5.1.x_Triage > > Using Add Node button in Navigation Management (Site or Group) always create new node at the top level. > When you have some subnode selected and Add Node button is used, node is created at the top level. > Only way to create subnode is to use context menu otherwise node selection is ignored. > Maybe it's wanted behavior, but IMO users would appreciate to create node on current selection. > Or is there reason for this behavior? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1969) CLONE - Need to provide a way to add customer javascript for each site

by Martin Weiler (JIRA)

CLONE - Need to provide a way to add customer javascript for each site ---------------------------------------------------------------------- Key: GTNPORTAL-1969 URL: https://issues.jboss.org/browse/GTNPORTAL-1969 Project: GateIn Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 3.0.0-GA Reporter: Martin Weiler Assignee: Khoi Nguyen Now we cannot add a customer javascript for each site. For example with SkinService we can add any customer stylesheet/css's path for each site, but we cannot do the same thing with javascript. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1933) actionScopedRequestAttributes not available for portlets

by m l (JIRA)

actionScopedRequestAttributes not available for portlets -------------------------------------------------------- Key: GTNPORTAL-1933 URL: https://issues.jboss.org/browse/GTNPORTAL-1933 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Common integration Affects Versions: 3.1.0-GA Environment: Java6 Reporter: m l javax.portlet.actionScopedRequestAttributes do not seem to be functioning. This blog post descibes what it should do: http://wpcertification.blogspot.com/2011/02/actionscopedrequestattributes... They make possible to call request.setAttribute() from processAction() to RenderRequest, to be available in the PortletFilter. There is a workaround by using response.setRenderParameter(), but I have a portlet that is already working in Liferay and I'd like to port it to GateIn by having this feature available. I have this in my portlet.xml: <container-runtime-option> <name>javax.portlet.actionScopedRequestAttributes</name> <value>true</value> </container-runtime-option> Still those attributes I set in processAction get lost, and are not available by RenderRequest.getAttribute() -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

4
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues July 2011