[JBoss JIRA] Created: (RFPL-1604) Metamer: rich:graphValidator: 2 examples on one page (MyFaces)
by Ján Jamrich (JIRA)
Metamer: rich:graphValidator: 2 examples on one page (MyFaces)
--------------------------------------------------------------
Key: RFPL-1604
URL: https://issues.jboss.org/browse/RFPL-1604
Project: RichFaces Planning
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.1.0.Milestone1
Environment: RichFaces 4.1.0.20110805-M1 r.10246d45dddd1d2aa2034317d5a832394cc919f9
Metamer 4.1.0.20110805-M1 r.22604
Apache MyFaces JSF-2.1 Core Impl 2.1.1
Apache Tomcat 7.0.19
Java(TM) SE Runtime Environment 1.6.0_26-b03 @Linux
Chrome 12.0.742.112 @ Linux i686, IE9
Reporter: Ján Jamrich
Example for rich:graphValidator consists from 2 instances of graphValidator - but one of then is not rendered due to current combination of attributes. But with MyFaces it seems that c:if condition is not handled correctly, and both examples are displayed in same time.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (RFPL-1851) Metamer: correct table width in some rich:extendedDataTable samples
by Jan Papousek (Created) (JIRA)
Metamer: correct table width in some rich:extendedDataTable samples
-------------------------------------------------------------------
Key: RFPL-1851
URL: https://issues.jboss.org/browse/RFPL-1851
Project: RichFaces Planning
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Affects Versions: 4.1.0.CR1
Reporter: Jan Papousek
Attachments: metamer-rich_extendedDataTable-filtering.png, metamer-rich_extendedDataTable-scroller.png, metamer-rich_extendedDataTable-selection.png, metamer-rich_extendedDataTable-sorting-using-column.png, metamer-rich_extendedDataTable-sorting-using-component-control.png
Some samples in metamer for rich:extendedDataTable contains a table which has a wrong width. It's little confusing, because it looks like a bug in the component, but it isn't.
--
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
11 years, 11 months
[JBoss JIRA] (RFPL-2330) can't run kitchensink archetype tests because the RuntimeException
by Jan Papousek (JIRA)
Jan Papousek created RFPL-2330:
----------------------------------
Summary: can't run kitchensink archetype tests because the RuntimeException
Key: RFPL-2330
URL: https://issues.jboss.org/browse/RFPL-2330
Project: RichFaces Planning
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.3.0.M1
Reporter: Jan Papousek
Assignee: Juraj Húska
The following exception is thrown:
{code}
java.lang.RuntimeException: Cannot locate /org/openqa/selenium/internal/seleniumemulation/selenium_atoms/isElementPresent.js
at org.openqa.selenium.internal.seleniumemulation.JavascriptLibrary.readScriptImpl(JavascriptLibrary.java:107)
at org.openqa.selenium.internal.seleniumemulation.JavascriptLibrary.readScript(JavascriptLibrary.java:97)
at org.openqa.selenium.internal.seleniumemulation.JavascriptLibrary.getSeleniumScript(JavascriptLibrary.java:52)
at org.openqa.selenium.internal.seleniumemulation.CompoundMutator.<init>(CompoundMutator.java:67)
at org.openqa.selenium.WebDriverCommandProcessor.<init>(WebDriverCommandProcessor.java:62)
at org.openqa.selenium.WebDriverCommandProcessor.<init>(WebDriverCommandProcessor.java:44)
at org.openqa.selenium.WebDriverBackedSelenium.<init>(WebDriverBackedSelenium.java:31)
at org.richfaces.tests.archetypes.kitchensink.ftest.common.AbstractKitchensinkTest.loadPage(AbstractKitchensinkTest.java:81)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:525)
at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:202)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:613)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:842)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1166)
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)
at org.testng.TestRunner.runWorkers(TestRunner.java:1178)
at org.testng.TestRunner.privateRun(TestRunner.java:757)
at org.testng.TestRunner.run(TestRunner.java:608)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
at org.testng.SuiteRunner.run(SuiteRunner.java:240)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1083)
at org.testng.TestNG.run(TestNG.java:999)
at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:177)
at org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:92)
at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:105)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:103)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
{code}
The error is caused by [this line|https://github.com/richfaces/qa/blob/20b9bdbb96116a5e820eb11deb97ccf...].
--
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
11 years, 11 months