March 2012 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12041) BeanValidator: no way to use BeanValidation with a custom config

by Markus Staab (JIRA)

Markus Staab created RF-12041: --------------------------------- Summary: BeanValidator: no way to use BeanValidation with a custom config Key: RF-12041 URL: https://issues.jboss.org/browse/RF-12041 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.3.3.Final Environment: Liferay 5.2.4, Portlet 2.0, JSF 1.2 Reporter: Markus Staab The BeanValidator class bootstraps a whole new BeanValidation context in its constructor: {code} BeanValidator() { // Enforce class to load ValidatorFactory.class.getName(); // Check Factory, to avoid instantiation errors // https://jira.jboss.org/jira/browse/RF-7226 validatorFactory = Validation .buildDefaultValidatorFactory(); validatorContext = validatorFactory.usingContext(); MessageInterpolator jsfMessageInterpolator = new JsfMessageInterpolator( validatorFactory.getMessageInterpolator()); validatorContext.messageInterpolator(jsfMessageInterpolator); } {/code} because of this, there is no way to use the programmatic configuration feature of BeanValidation. I tried to pre-configure a custom MessageInterpolator with {code} Configuration<?> config = Validation.byDefaultProvider().configure(); config.messageInterpolator( new MyInterpolator() ); {/code} but this configuration change is not taken into account by the BeanValidator of Richfaces. ATM the only way to achive this sort of customization is to use a META-INF/validation.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
4
0 / 0

[JBoss JIRA] (RF-12065) Continuous event polling in available.js

by Nicholas Oxhøj (JIRA)

Nicholas Oxhøj created RF-12065: ----------------------------------- Summary: Continuous event polling in available.js Key: RF-12065 URL: https://issues.jboss.org/browse/RF-12065 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.3.3.Final Reporter: Nicholas Oxhøj Priority: Minor In available.js there is two functions activatePolling() and stopPolling(), used to wait for a specific DOM element becoming available. But while activatePolling() starts observing the events "*mousemove*", "focus", and "focusin", stopPolling() stops observing the events "*mouseover*", "focus", and "focusin" - which means that it will _keep_ calling onEvent() on every "mousemove", even when the relevant element has already been found... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
2
0 / 0

[JBoss JIRA] (RF-11872) Mobile Showcase and a4j:region demo: submit button doesn't respond on the first click

by Jan Papousek (Created) (JIRA)

Mobile Showcase and a4j:region demo: submit button doesn't respond on the first click ------------------------------------------------------------------------------------- Key: RF-11872 URL: https://issues.jboss.org/browse/RF-11872 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: mobile, showcase Affects Versions: 4.1.1.Final Environment: richfaces-showcase-4.1.1-20120106.230242-18 Reporter: Jan Papousek -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
14
0 / 0

[JBoss JIRA] (RF-12048) Change the password for JMS guest connection

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-12048: ------------------------------- Summary: Change the password for JMS guest connection Key: RF-12048 URL: https://issues.jboss.org/browse/RF-12048 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: component-push/poll Affects Versions: 4.2.0.Final Reporter: Lukáš Fryč [Originally request|https://issues.jboss.org/browse/RF-11983?focusedCommentId=1267671...] by Karel Piwko: AS7 doesn't allow to add user with same name and password, that's why having {{guest:guest}} credentials [1] does not make sense. We can change the credentials to {{guest:password}} - I have verified the actual content does not have any influence on functionality on AS7.0 and will improve usability on AS7.1. [1] https://github.com/richfaces/showcase/blob/4.2.0.20120215-Final/src/main/... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
6
0 / 0

[JBoss JIRA] (RF-12027) Add a maximum number of selectable elements to rich:pickList

by Karsten Wutzke (JIRA)

Karsten Wutzke created RF-12027: ----------------------------------- Summary: Add a maximum number of selectable elements to rich:pickList Key: RF-12027 URL: https://issues.jboss.org/browse/RF-12027 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Environment: any Reporter: Karsten Wutzke Please add a maximum number of selectable elements to rich:pickList via an attribute like maxItems="n" or maxValues="n" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
1
0 / 0

[JBoss JIRA] (RF-12009) Showcase: page header in Opera Mobile

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-12009: ------------------------------- Summary: Showcase: page header in Opera Mobile Key: RF-12009 URL: https://issues.jboss.org/browse/RF-12009 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: mobile Affects Versions: 4.2.0.Final Environment: http://showcase.richfaces.org/ Opera Mobile v 12.00.ADR-1202131246 Reporter: Lukáš Fryč -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
8
0 / 0

[JBoss JIRA] (RF-11971) rich:menuItem onclick return value ignored

by Brendan Healey (JIRA)

Brendan Healey created RF-11971: ----------------------------------- Summary: rich:menuItem onclick return value ignored Key: RF-11971 URL: https://issues.jboss.org/browse/RF-11971 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.0.Final Environment: Chrome / glassfish 3.1.1 / mojarra 2.1.6 Reporter: Brendan Healey My expectation was that using rich:menuItem onclick="if(!confirm('#{msgs.playerConfirmDelete}')) return false;" (and selecting cancel) would prevent any action routines being called, as is common with components such as h:commandButton. As it stands the return value is ignored and processing continues with return true or return false. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

5
14
0 / 0

[JBoss JIRA] Created: (RF-10941) a4j:command* components misses default behavior event

by Ilya Shaikovsky (JIRA)

a4j:command* components misses default behavior event ----------------------------------------------------- Key: RF-10941 URL: https://issues.jboss.org/browse/RF-10941 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-a4j-core Affects Versions: 4.0.0.Final Reporter: Ilya Shaikovsky http://community.jboss.org/message/601191#601191 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

5
20
0 / 0

[JBoss JIRA] (RF-12056) CDK ignores default-behavior value in props.xml file

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12056?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč deleted RF-12056: ---------------------------- > CDK ignores default-behavior value in props.xml file > ---------------------------------------------------- > > Key: RF-12056 > URL: https://issues.jboss.org/browse/RF-12056 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > > In the initial issue, the {{defaultEventName}} is not provided. > The problem is CDK recognizes default event name from annotation (@Attribute(event=@EventName(defaultEvent=true, ...))}, but not from XML configuration {{<default-behavior>true</default-behavior>}}. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RF-12056) CDK ignores default-behavior value in props.xml file

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-12056: ------------------------------- Summary: CDK ignores default-behavior value in props.xml file Key: RF-12056 URL: https://issues.jboss.org/browse/RF-12056 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: cdk Affects Versions: 4.2.0.Final Reporter: Lukáš Fryč Assignee: Lukáš Fryč In the initial issue, the {{defaultEventName}} is not provided. The problem is CDK recognizes default event name from annotation (@Attribute(event=@EventName(defaultEvent=true, ...))}, but not from XML configuration {{<default-behavior>true</default-behavior>}}. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues March 2012