May 2011 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Created: (RF-10962) status and timer problem

by Carl Johnson (JIRA)

status and timer problem ------------------------ Key: RF-10962 URL: https://issues.jboss.org/browse/RF-10962 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-push/poll Affects Versions: 4.0.0.Final Environment: OS Linux, Glassfish 3, JSF 2, RichFaces 4 Reporter: Carl Johnson Fix For: 4.0.0.Final Have no idea how to make poll be irresponsible to status. The problem appears while using poll inside a tab. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (RF-10954) rich:graphValidator doesn't work with rich:messages globalOnly="true"

by Juergen Zimmermann (JIRA)

rich:graphValidator doesn't work with rich:messages globalOnly="true" --------------------------------------------------------------------- Key: RF-10954 URL: https://issues.jboss.org/browse/RF-10954 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-validators Affects Versions: 4.0.0.Final Reporter: Juergen Zimmermann The following tags are only working when I omit globalOnly="true". I'll attach 2 screenshots to illustrate the issue. {{monospaced}} <h:form id="createKundeForm"> <rich:graphValidator id="kundeValidator" value="#{kv.neuerPrivatkunde}" groups="de.swe2.kundenverwaltung.domain.PasswordGroup"> <rich:messages id="fehlermeldungPassword" globalOnly="true" /> <p/> <h:panelGrid id="createKundeTabelle" columns="3"> <h:outputLabel id="nachnameLabel" for="nachname" value="#{msgKv['createPrivatkunde.nachname']}"/> <h:inputText id="nachname" value="#{kv.neuerPrivatkunde.nachname}"> <rich:validator/> </h:inputText> <rich:messages id="fehlermeldungenNachname" for="nachname"/> ... {{monospaced}} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
7
0 / 0

[JBoss JIRA] Created: (RF-10995) datagrid: suppress empty columns

by u j (JIRA)

datagrid: suppress empty columns -------------------------------- Key: RF-10995 URL: https://issues.jboss.org/browse/RF-10995 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: component-tables Affects Versions: 4.0.0.Final Reporter: u j Priority: Minor When the number of elements in a rich:dataGrid is less than expected, empty columns are created. It would be nice to have an attribute like "noEmptyColumns" to suppress those. Currently you have to use a clumsy workaround like columns="#{fn:length(bean.result) lt 4 ? fn:length(bean.result) : 4}" -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (RF-10955) The tag <rich:tooltip> is misspelled in the documentation examples.

by Daniel Görlich (JIRA)

The tag <rich:tooltip> is misspelled in the documentation examples. ------------------------------------------------------------------- Key: RF-10955 URL: https://issues.jboss.org/browse/RF-10955 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.0.0.Final Reporter: Daniel Görlich Priority: Trivial The tag <rich:tooltip> is misspelled in the documentation examples (<rich:toolTip ../>). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (RF-10943) SuggestionBox: why no "converter" attribute?

by Markus Staab (JIRA)

SuggestionBox: why no "converter" attribute? -------------------------------------------- Key: RF-10943 URL: https://issues.jboss.org/browse/RF-10943 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.2.1 Reporter: Markus Staab Assignee: Mikhail Vitenkov Fix For: 3.2.2 "converter" attribute of rich:suggestionbox component should be deleted. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
16
0 / 0

[JBoss JIRA] Created: (RF-11006) Showcase running on JBoss AS 7

by Lukáš Fryč (JIRA)

Showcase running on JBoss AS 7 ------------------------------ Key: RF-11006 URL: https://issues.jboss.org/browse/RF-11006 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: examples Affects Versions: 4.1.0.Milestone1 Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 4.1.0.Milestone1 Create separated profile jboss-as7 to be able generate WAR running on JBoss AS 7. It have to contain persistence.xml with <non-jta-data-source>java:/ -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (RF-11005) Showcase isn't deployable on JBoss AS 6 (missing non-jta-data-source)

by Lukáš Fryč (JIRA)

Showcase isn't deployable on JBoss AS 6 (missing non-jta-data-source) --------------------------------------------------------------------- Key: RF-11005 URL: https://issues.jboss.org/browse/RF-11005 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: examples Affects Versions: 4.1.0.Milestone1 Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 4.1.0.Milestone1 Latest changes (RF-10845) seems to break compatibility with JBoss AS 6. There are problems with persistence.xml configuration. We need to add non-jta-data-source to XML to let it work on AS6. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (RF-10997) @Test annotation param dependsOnMethods in Metamer's ftest causes IllegalStateException

by Jan Jamrich (JIRA)

@Test annotation param dependsOnMethods in Metamer's ftest causes IllegalStateException --------------------------------------------------------------------------------------- Key: RF-10997 URL: https://issues.jboss.org/browse/RF-10997 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Environment: Metamer 4.1.0-snapshot, r.22501 Reporter: Jan Jamrich When tried set dependsOnMethods param to @Test annotation in Metamer's ftests, get IllegalStateException thrown from MatrixConfigurator. There aren't any other methods annotated by @Test with dependsOnMethods param, so its possible that this issue is in Metamer longer time without being discovered. By debugging observed that list of methods set to be executed by TestRunner depends on this param. In other word, when set dependsOnMethods param to @Test annotation - this method (on which was this param set to annotation) doesn't appear in list of methods being executed (LinkedList<Method> methods attribute of MatrixConfigurator). This attribute is initialized in method public List<IMethodInstance> intercept(List<IMethodInstance> methodInstances, ITestContext context) which is called directly from org.testng.TestRunner, which give param List<IMethodInstance> methodInstances depending on dependsOnMethods param set to @Test annotation as well. This behavior should be ok, since methods which are not depending on another else method should be executed first. But what seems worse is that when run this again - for method anotated by @Test with param dependsOnMethod, then list of methods which going to be executed is empty - do no test method called. And in case when all methods except one depends on another method, different exception is result of run testsuite: Running TestSuite org.apache.maven.surefire.booter.SurefireExecutionException: null; nested exception is java.lang.NullPointerException: null java.lang.NullPointerException at org.richfaces.tests.metamer.ftest.MetamerTestInfo.getConfigurationInfo(MetamerTestInfo.java:50) at org.richfaces.tests.metamer.ftest.MetamerTestInfo.getConfigurationInfoInParenthesses(MetamerTestInfo.java:77) at org.richfaces.tests.metamer.ftest.MetamerSeleniumLoggingTestListener.getMessage(MetamerSeleniumLoggingTestListener.java:35) at org.jboss.test.selenium.listener.SeleniumLoggingTestListener.logStatus(SeleniumLoggingTestListener.java:82) at org.jboss.test.selenium.listener.SeleniumLoggingTestListener.onTestFailure(SeleniumLoggingTestListener.java:55) at org.testng.internal.Invoker.runTestListeners(Invoker.java:1634) at org.testng.internal.Invoker.runTestListeners(Invoker.java:1618) at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1101) at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:137) at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:121) at org.testng.TestRunner.runWorkers(TestRunner.java:1030) at org.testng.TestRunner.privateRun(TestRunner.java:709) at org.testng.TestRunner.run(TestRunner.java:579) at org.testng.SuiteRunner.runTest(SuiteRunner.java:331) at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:326) at org.testng.SuiteRunner.privateRun(SuiteRunner.java:288) at org.testng.SuiteRunner.run(SuiteRunner.java:193) at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:910) at org.testng.TestNG.runSuitesLocally(TestNG.java:879) at org.testng.TestNG.run(TestNG.java:787) at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:62) at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:141) at org.apache.maven.surefire.Surefire.run(Surefire.java:177) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009) So this should be issue related to TestNG itself (current version 5.12.1), tried 5.13, but the same behavior. There is stack trace: java.lang.IllegalStateException: can't find more configured methods at org.richfaces.tests.metamer.ftest.MatrixConfigurator.configureMethod(MatrixConfigurator.java:150) at org.richfaces.tests.metamer.ftest.MatrixConfigurator.beforeInvocation(MatrixConfigurator.java:101) at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:62) at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:141) at org.apache.maven.surefire.Surefire.run(Surefire.java:177) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009) ... Removed 22 stack frames -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (RF-6525) rich:fileUpload createTempfiles directory should be made configurable.

by sathay sayee (JIRA)

rich:fileUpload createTempfiles directory should be made configurable. ---------------------------------------------------------------------- Key: RF-6525 URL: https://jira.jboss.org/jira/browse/RF-6525 Project: RichFaces Issue Type: Bug Affects Versions: 3.3.0 Environment: All Reporter: sathay sayee rich:fileUpload control's createTempFile can be configured as init-param in web.xml. The real problem is when createTempfile is true, the temp files in linux environment gets created in the <tomcat installation directory>/temp. This should be configurable and poses a security risk since the temp files do not even get deleted until the application is restarted. -- 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, 6 months

9
11
0 / 0

[JBoss JIRA] Created: (RF-8338) Some RichFaces components strip white space

by Brian Chicos (JIRA)

Some RichFaces components strip white space ------------------------------------------- Key: RF-8338 URL: https://jira.jboss.org/jira/browse/RF-8338 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-output Environment: RichFaces 3.3.1 libraries w/ JBOSS EAP 4.3 Reporter: Brian Chicos Fix For: 3.3.1 RichFaces seems to be stripping out extra white space in data before sending it to the browser. I see this for data being displayed in both the rich:dataTable and rich:suggestionbox components. If there is data that has multiple spaces next to each other (ex: this data) it will get returned with a single space (ex: this data). This creates a problem especially on the rich:suggestionbox component. If the data being searched on has 2 spaces and the rich:suggestionbox returns the data with one space then the search will fail when the value is selected from the suggestionbox and the user then attempts to run the search. It seems that RichFaces should send back the data from the server without altering it and let the browser decide how to display it. -- 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, 6 months

4
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues May 2011