June 2011 - richfaces-planning-issues

[JBoss JIRA] Created: (RFPL-634) Verify/Work with JBoss tools to get 4.0 visual editor palette up-to-date

by Jay Balunas (JIRA)

Verify/Work with JBoss tools to get 4.0 visual editor palette up-to-date ------------------------------------------------------------------------ Key: RFPL-634 URL: https://jira.jboss.org/browse/RFPL-634 Project: RichFaces Planning Issue Type: Task Security Level: Public (Everyone can see) Components: administration Reporter: Jay Balunas Fix For: 4.0.0.M1 There was talk a while ago about developing a standard way of defining components so that JBoss tools can pull updates automatically to keep palette up to date. We need to follow up on this, and make sure we at the very least get out initial components in place -- 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

12 years, 10 months

3
8
0 / 0

[JBoss JIRA] Created: (RFPL-1462) Add an options "push" example into showcase demo

by Jay Balunas (JIRA)

Add an options "push" example into showcase demo ------------------------------------------------ Key: RFPL-1462 URL: https://issues.jboss.org/browse/RFPL-1462 Project: RichFaces Planning Issue Type: Task Security Level: Public (Everyone can see) Components: examples Reporter: Jay Balunas Fix For: 4.1.0.Milestone1 As we are moving to Red Hat openshift for the showcase demo - this provides us an opportunity to have a push demo added to ( or updated ) for the showcase. The demo should show * Options for sending messages ** RichFaces TopicContext ** Direct JMS ** CDI ( when completed ) * Options for processing on client ** Notification of updates, and trigger an ajax render ** Sending of data for on client processing. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

2
7
0 / 0

[JBoss JIRA] Created: (RFPL-1127) Setup redirector for hosted showcase

by Nick Belaevski (JIRA)

Setup redirector for hosted showcase ------------------------------------ Key: RFPL-1127 URL: https://issues.jboss.org/browse/RFPL-1127 Project: RichFaces Planning Issue Type: Task Security Level: Public (Everyone can see) Components: examples Affects Versions: 4.0.0.CR1 Reporter: Nick Belaevski Assignee: Jay Balunas Setup redirector pointing to the currently deployed version of showcase in order to be able to move it to another hosting easily. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (RFPL-1331) Create a "How to use RichFaces 4 with Google AppEngine" wiki page

by Jay Balunas (JIRA)

Create a "How to use RichFaces 4 with Google AppEngine" wiki page ----------------------------------------------------------------- Key: RFPL-1331 URL: https://issues.jboss.org/browse/RFPL-1331 Project: RichFaces Planning Issue Type: Task Security Level: Public (Everyone can see) Components: examples, site, third-party Reporter: Jay Balunas Assignee: Jay Balunas Fix For: Site We need a common wiki page where the various information on running RichFaces 4.0 ( plus JSF 2.0 ) can be compiled. It should start out with a walk through of getting the showcase uploaded, and describing in more detail than the readme.txt the updates that were made to make it run well. This page could then further expand to include more detailed information on optimizations, and other aspects. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (RFPL-815) Update component development guide with sandbox rules

by Jay Balunas (JIRA)

Update component development guide with sandbox rules ----------------------------------------------------- Key: RFPL-815 URL: https://jira.jboss.org/browse/RFPL-815 Project: RichFaces Planning Issue Type: Task Security Level: Public (Everyone can see) Components: administration, site Reporter: Jay Balunas Assignee: Jay Balunas Fix For: 4.0.0.Milestone4 This includes how to get access, updating https://community.jboss.org/wiki/40SandboxComponents page, and how to move items in/out of 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

12 years, 10 months

1
5
0 / 0

[JBoss JIRA] Created: (RFPL-1476) Verify styling of components

by Lukáš Fryč (JIRA)

Verify styling of components ---------------------------- Key: RFPL-1476 URL: https://issues.jboss.org/browse/RFPL-1476 Project: RichFaces Planning Issue Type: Task Security Level: Public (Everyone can see) Components: QE Affects Versions: 4.0.0.Final Reporter: Lukáš Fryč Assignee: Pavol Pitonak We need to develop new principles to test styles of components in Metamer. It includes the mechanism for resolving style which is really applied to given component part. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
1
0 / 0

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

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RFPL-1467?page=com.atlassian.jira.plugin.... ] Pavol Pitonak updated RFPL-1467: -------------------------------- Fix Version/s: 4.Future > @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 > Fix For: 4.Future > > > 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (RFPL-1428) QE: w3c validation test should be performed for components(major) and demos(minor)

by Ilya Shaikovsky (JIRA)

QE: w3c validation test should be performed for components(major) and demos(minor) ---------------------------------------------------------------------------------- Key: RFPL-1428 URL: https://issues.jboss.org/browse/RFPL-1428 Project: RichFaces Planning Issue Type: Task Security Level: Public (Everyone can see) Components: QE Affects Versions: 4.0.0.Final Reporter: Ilya Shaikovsky Assignee: Jay Balunas Will be especially important for product support. So need to include into process and checklist. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

3
2
0 / 0

[JBoss JIRA] Created: (RFPL-1438) Test dynamic creation of components

by Lukáš Fryč (JIRA)

Test dynamic creation of components ----------------------------------- Key: RFPL-1438 URL: https://issues.jboss.org/browse/RFPL-1438 Project: RichFaces Planning Issue Type: Task Security Level: Public (Everyone can see) Components: QE Affects Versions: 4.0.0.Final Reporter: Lukáš Fryč Assignee: Pavol Pitonak -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (RFPL-748) Metamer Ftest - add automatic markup validation feature

by Lukas Fryc (JIRA)

Metamer Ftest - add automatic markup validation feature ------------------------------------------------------- Key: RFPL-748 URL: https://jira.jboss.org/browse/RFPL-748 Project: RichFaces Planning Issue Type: Feature Request Security Level: Public (Everyone can see) Components: QA Affects Versions: 4.0.0.Milestone1 Reporter: Lukas Fryc Assignee: Lukas Fryc Fix For: 4.0.0.Milestone3 At least one browser should be configured to automatically validate markup during functional test (probably Firefox). -- 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

12 years, 11 months

3
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

richfaces-planning-issues June 2011