[JBoss JIRA] (RF-11805) a4j:queue onerror doesn't seem to work
by Brendan Healey (Created) (JIRA)
a4j:queue onerror doesn't seem to work
--------------------------------------
Key: RF-11805
URL: https://issues.jboss.org/browse/RF-11805
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.1.0.CR2
Reporter: Brendan Healey
I was just testing some 'global' ajax error handling code. I put an <a4j:queue onerror="alert('A')"/>
outside a form, then forced an ajax error like this:
<h:inputText>
<a4j:ajax event="blur" listener="#{myBean.forceAjaxError}"/>
</h:inputText>
public void forceAjaxError(AjaxBehaviorEvent event) {
getResponse().setStatus(501);
}
public HttpServletResponse getResponse() {
return (HttpServletResponse) FacesContext.getCurrentInstance().getExternalContext().getResponse();
}
so I click into and out of the input, the ajax POST request completes with a 501 status but no alert is shown.
I just tried it with a4j:status and this does pick up the error.
--
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
13 years, 10 months
[JBoss JIRA] (RF-11972) Rich select : cutomize the css on error by a filter - rendered implementation
by Jean ANDRE (JIRA)
Jean ANDRE created RF-11972:
-------------------------------
Summary: Rich select : cutomize the css on error by a filter - rendered implementation
Key: RF-11972
URL: https://issues.jboss.org/browse/RF-11972
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.1.0.CR2
Environment: Firefox 10 - Jsf 2.1.4 - cssparser-0.9.6 - guava-11.0.1 - sac-1.3 - Spring Core -3.0.6 - Windows 7 - WAS 8.0.0.1 - RAD 8.0.0.4 - hibernate-validator-4.2.0
Reporter: Jean ANDRE
The way how the rich:select is rendered in HTML breaks the consistency with the JSF component h:selectXXX - It requires to know the detail implementation or it is impossible to achieve the goal.
What we want to achieve is to highlight in red the border of the combo/list box when some validation rules failed.
The problem is that the red border is not "close" to the component as a calendar is or as a h:select is. More over, it is impossible to retrieve the inner elements through the view root (UIViewRoot) or it force us to know the detail implementation of the rich:select to be able to achieve our goal.
Actually, the implementation of rich:select is pretty complex - The problem comes from the first div - should be a span as rich:calendar ?
After several years, I'm still surprising that there is no easy way to achieve the customization of a component based on error - Having a such attribute as "errorClass" will help or having a uniform way to indicate us when a component is in error or not. Can we expose the isValid (http://docs.oracle.com/javaee/6/api/javax/faces/component/UIInput.html) flag ?
--
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
13 years, 10 months
[JBoss JIRA] (RF-11783) disabled a4j:commandButton with nested tooltip disappears when enabled with ajax render
by Brendan Healey (Created) (JIRA)
disabled a4j:commandButton with nested tooltip disappears when enabled with ajax render
---------------------------------------------------------------------------------------
Key: RF-11783
URL: https://issues.jboss.org/browse/RF-11783
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.1.0.Milestone4
Environment: Mojarra 2.1.3, Glassfish 3.1.1.
Reporter: Brendan Healey
The following code resides in the footer of an extendedDataTable, although my
guess is that this is not relevant. The button is initially disabled, then
bean.property is set true and we do ajax render="myButton". The button
disappears from the screen. Removing the tooltip makes it work as expected.
<a4j:commandButton
id="myButton"
value=" test "
action="apage?faces-redirect=true"
disabled="#{empty bean.property}">
<rich:tooltip mode="client" showDelay="850">
<h:panelGroup layout="block" style="width: 200px; text-align: justify">
<h:outputText escape="false" value="some text"/>
</h:panelGroup>
</rich:tooltip>
</a4j:commandButton>
--
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
13 years, 10 months
[JBoss JIRA] (RF-11782) [rich:tabPanel] switching tabs doesn't work correctly with switchtype="ajax"
by Rene O (Created) (JIRA)
[rich:tabPanel] switching tabs doesn't work correctly with switchtype="ajax"
----------------------------------------------------------------------------
Key: RF-11782
URL: https://issues.jboss.org/browse/RF-11782
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.1.0.CR1
Environment: mojarra-2.1.4, RF-CR1
Reporter: Rene O
A testcase to reproduce this issue is attached:
http://localhost:8080/jsf2testcase/tabswitchtest.jsf
Steps to reproduce the issue:
1. switch to 'Tab 3' -> console/server-log shows 'getTestListA' and 'getTestListB' -> this is a bug, expected is only 'getTestListB', because tab3 has only one table with testListB
2. switch to 'Tab 1' -> console/server-log shows 'getTestListB' -> this is a bug, expected is nothing new in console/server-log, because tab1 has no table
{code:title=xhtml}
...
<h:form id="testform">
<rich:tabPanel id="tabpanel" switchType="ajax" activeItem="#{dataBean.activeTab}">
<rich:tab id="tab1" header="Tab 1">
Here is tab #1
</rich:tab>
<rich:tab id="tab2" header="Tab 2">
<rich:dataTable value="#{dataBean.testListA}" var="item" rows="10">
<rich:column >
<f:facet name="header">
List A
</f:facet>
h:outputText value="#{item.a}"/>
</rich:column>
</rich:dataTable>
</rich:tab>
<rich:tab id="tab3" header="Tab 3">
<rich:dataTable value="#{dataBean.testListB}" var="item" rows="10">
<rich:column >
<f:facet name="header">
List B
</f:facet>
<h:outputText value="#{item.a}"/>
</rich:column>
</rich:dataTable>
</rich:tab>
</rich:tabPanel>
</h:form>
...
{code}
{code:title=java}
...
public List<TestObject> getTestListA() {
System.out.println("getTestListA");
return testListA;
}
...
public List<TestObject> getTestListB() {
System.out.println("getTestListB");
return testListB;
}
...
{code}
--
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
13 years, 10 months
[JBoss JIRA] (RF-11793) Fix unstable test OsCacheTest.testExpiration
by Lukáš Fryč (Created) (JIRA)
Fix unstable test OsCacheTest.testExpiration
--------------------------------------------
Key: RF-11793
URL: https://issues.jboss.org/browse/RF-11793
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: tests - unit
Affects Versions: 4.1.0.CR2
Reporter: Lukáš Fryč
Assignee: Lukáš Fryč
org.richfaces.cache.OsCacheTest.testExpiration
expected:<value-a> but was:<null>
Stacktrace
junit.framework.AssertionFailedError: expected:<value-a> but was:<null>
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.failNotEquals(Assert.java:277)
at junit.framework.Assert.assertEquals(Assert.java:64)
at junit.framework.Assert.assertEquals(Assert.java:71)
at org.richfaces.cache.BaseCacheTest.testExpiration(BaseCacheTest.java:102)
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 junit.framework.TestCase.runTest(TestCase.java:168)
at junit.framework.TestCase.runBare(TestCase.java:134)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at junit.framework.TestSuite.runTest(TestSuite.java:232)
at junit.framework.TestSuite.run(TestSuite.java:227)
at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:59)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:115)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:102)
at org.apache.maven.surefire.Surefire.run(Surefire.java:180)
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:350)
at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1021)
--
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
13 years, 10 months