May 2011 - richfaces-planning-issues

[JBoss JIRA] Created: (RFPL-1355) Create a series of "how to" wiki pages for various development/project tasks

by Jay Balunas (JIRA)

Create a series of "how to" wiki pages for various development/project tasks ---------------------------------------------------------------------------- Key: RFPL-1355 URL: https://issues.jboss.org/browse/RFPL-1355 Project: RichFaces Planning Issue Type: Task Security Level: Public (Everyone can see) Components: administration, site Reporter: Jay Balunas Assignee: Jay Balunas Priority: Critical Fix For: 4.0.1.Milestone1 This is an umbrella tasks for creating a series of how to wiki pages that describe various project tasks. These will include: * Development environment set up ** Workflow ** Debugging techniques ** Server set ups * Component development ** Getting started ** Migration from 3.3.X ** Client side considerations * CDK ** General features and use-cases ** Plugin development * Skinning * Hints and tips This should include screenshots, diagrams, and be from the perspective of someone who is familiar with JSF usage, IDE's, Maven, JBoss, Tomcat, etc... I.e. does not need to be a "how to start from nothing". -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (RFPL-856) Migration investigation 3.3 --> 4.0

by Jay Balunas (JIRA)

Migration investigation 3.3 --> 4.0 ----------------------------------- Key: RFPL-856 URL: https://jira.jboss.org/browse/RFPL-856 Project: RichFaces Planning Issue Type: Task Security Level: Public (Everyone can see) Components: administration, components, core, examples Reporter: Jay Balunas Assignee: Ilya Shaikovsky Priority: Critical Fix For: 4.0.0.Milestone4 As discussed at JavaOne, please begin initial investigation and migration of a 3.3.X example to 4.0.0. Be careful to note down all steps required. Please also create a thread, or wiki page to track and review issues, and progress. -- 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

14 years, 11 months

2
9
0 / 0

[JBoss JIRA] Created: (RFPL-1482) rich:inplaceSelect suggestions disappear when move scroller (in Chrome)

by Ján Jamrich (JIRA)

rich:inplaceSelect suggestions disappear when move scroller (in Chrome) ----------------------------------------------------------------------- Key: RFPL-1482 URL: https://issues.jboss.org/browse/RFPL-1482 Project: RichFaces Planning Issue Type: Bug Security Level: Public (Everyone can see) Components: QE Environment: RichFaces ShowCase, Metamer 4.1.0-SNAPSHOT Reporter: Ján Jamrich When move scroller by mouse in rich:inplaceSelect without confirmation button (immediate selection) in Chrome browser, whole pop-up with selects disappear. But scroller works corectly in Forefox. I made some test changes in ShowCase - added more options into first inplaceSelect -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (RFPL-1447) Migrate tests from EasyMock to Mockito

by Lukáš Fryč (JIRA)

Migrate tests from EasyMock to Mockito -------------------------------------- Key: RFPL-1447 URL: https://issues.jboss.org/browse/RFPL-1447 Project: RichFaces Planning Issue Type: Task Security Level: Public (Everyone can see) Reporter: Lukáš Fryč Assignee: Lukáš Fryč -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (RFPL-1408) CustomBehaviorHandler: provide better name for the class and remove ComponentControlHandler from descendants

by Nick Belaevski (JIRA)

CustomBehaviorHandler: provide better name for the class and remove ComponentControlHandler from descendants ------------------------------------------------------------------------------------------------------------ Key: RFPL-1408 URL: https://issues.jboss.org/browse/RFPL-1408 Project: RichFaces Planning Issue Type: Task Security Level: Public (Everyone can see) Reporter: Nick Belaevski CustomBehaviorHandler is base class for Ajax behaviors that should be compatible with a4j:attachQueue tag, so the class should get better name and ComponentControlHandler should not be inherited from it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (RFPL-1420) Autocomplete - @fetchValue attribute is not covered in docs

by Lukas Fryc (JIRA)

Autocomplete - @fetchValue attribute is not covered in docs ----------------------------------------------------------- Key: RFPL-1420 URL: https://issues.jboss.org/browse/RFPL-1420 Project: RichFaces Planning Issue Type: Bug Security Level: Public (Everyone can see) Components: doc Affects Versions: 4.0.0.Final Reporter: Lukas Fryc -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (RFPL-1429) rich:DataTableEdit in poppup is possible to asign negative values to price and mileage inputs

by Juraj Huska (JIRA)

rich:DataTableEdit in poppup is possible to asign negative values to price and mileage inputs --------------------------------------------------------------------------------------------- Key: RFPL-1429 URL: https://issues.jboss.org/browse/RFPL-1429 Project: RichFaces Planning Issue Type: Bug Security Level: Public (Everyone can see) Components: examples Affects Versions: 4.0.0.Final Environment: richfaces-showcase Reporter: Juraj Huska In the poppup there is possibility to assign negative values to price and mileage inputs, since there is <f:validateDoubleRange/> but without correct range assigned, there also should be information about that range, to let user know what values are correct. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (RFPL-1442) Document rich:autocomplete layouts

by Lukáš Fryč (JIRA)

Document rich:autocomplete layouts ---------------------------------- Key: RFPL-1442 URL: https://issues.jboss.org/browse/RFPL-1442 Project: RichFaces Planning Issue Type: Task Security Level: Public (Everyone can see) Components: doc Affects Versions: 4.0.0.Final Reporter: Lukáš Fryč -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
1
0 / 0

[JBoss JIRA] Assigned: (RFPL-1467) @Test annotation param dependsOnMethods in Metamer's ftest causes IllegalStateException

by Jay Balunas (JIRA)

[ https://issues.jboss.org/browse/RFPL-1467?page=com.atlassian.jira.plugin.... ] Jay Balunas reassigned RFPL-1467: --------------------------------- Assignee: Pavol Pitonak > @Test annotation param dependsOnMethods in Metamer's ftest causes IllegalStateException > --------------------------------------------------------------------------------------- > > Key: RFPL-1467 > URL: https://issues.jboss.org/browse/RFPL-1467 > Project: RichFaces Planning > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: QE > Environment: Metamer 4.1.0-snapshot, r.22501 > Reporter: Ján Jamrich > Assignee: Pavol Pitonak > > 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

14 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (RFPL-1392) Document when it is needed to bind table to model

by Jay Balunas (JIRA)

[ https://issues.jboss.org/browse/RFPL-1392?page=com.atlassian.jira.plugin.... ] Jay Balunas updated RFPL-1392: ------------------------------ Fix Version/s: 4.Future > Document when it is needed to bind table to model > ------------------------------------------------- > > Key: RFPL-1392 > URL: https://issues.jboss.org/browse/RFPL-1392 > Project: RichFaces Planning > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.0.0.Final > Reporter: Lukáš Fryč > Fix For: 4.Future > > > There is need to bind table to the managed been - when using sorting/filtering. > Not sure about particular situation when it is needed but should be documented. > Nick, Ilya, please provide more details and sample to document it properly. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

richfaces-planning-issues May 2011