[JBoss JIRA] (RF-11919) showcase - names of some samples do not follow camel case naming convention
by Juraj Huska (JIRA)
Juraj Huska created RF-11919:
--------------------------------
Summary: showcase - names of some samples do not follow camel case naming convention
Key: RF-11919
URL: https://issues.jboss.org/browse/RF-11919
Project: RichFaces
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Reporter: Juraj Huska
There are some samples in showcase which do not follow camel case naming convention. First of all it is inconsistent with other sample names and secondly it makes some problems with showcase tests, since I am using method for loading the appropriate page according to the test class name, which should be obviously named using camel case. Can you please rename following samples ?
component demo - sample
########################
a4j:status - viewusage, referencedusage
a4j:outputPanel - Auto update for h:messages component
--
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, 11 months
[JBoss JIRA] (RF-11922) Nesting an a4j:actionListener in a composite component results in a java.io.NotSerializableException
by Brian Leathem (JIRA)
Brian Leathem created RF-11922:
----------------------------------
Summary: Nesting an a4j:actionListener in a composite component results in a java.io.NotSerializableException
Key: RF-11922
URL: https://issues.jboss.org/browse/RF-11922
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-a4j-core
Affects Versions: 4.1.0.Final
Reporter: Brian Leathem
Fix For: 4.Future
In the code samples below, an a4j:actionListener is nested in a composite component. This results in a java.io.NotSerializableException (stack trace below).
{code:title=actionComposite.xhtml}
<composite:interface>
<composite:actionSource name="button" />
<composite:attribute name="render" />
<composite:attribute name="execute" />
<composite:attribute name="value" />
</composite:interface>
<composite:implementation>
<h:commandButton id="button" value="#{cc.attrs.value}">
<composite:insertChildren />
<f:ajax render="#{cc.attrs.render}" execute="#{cc.attrs.execute}" />
</h:commandButton>
</composite:implementation>
</html>
{code}
{code:title=actionListener.xhtml}
<h:form id="form">
<h:messages id="messages" />
<h:panelGrid columns="1">
<demo:actionComposite render=":form:messages" value="Invoke listener method in composite component">
<a4j:actionListener for="button" listener="#{actionListenerBean.handleActionMethodComposite}" />
</demo:actionComposite>
</h:panelGrid>
</h:form>
{code}
{code:title=Stacktrace}
Caused by: java.io.NotSerializableException: org.richfaces.view.facelets.html.ActionListenerHandler
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1164) [:1.6.0_26]
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330) [:1.6.0_26]
at java.util.ArrayList.writeObject(ArrayList.java:570) [:1.6.0_26]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_26]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_26]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_26]
at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_26]
at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945) [:1.6.0_26]
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1469) [:1.6.0_26]
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400) [:1.6.0_26]
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158) [:1.6.0_26]
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518) [:1.6.0_26]
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483) [:1.6.0_26]
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400) [:1.6.0_26]
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158) [:1.6.0_26]
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330) [:1.6.0_26]
at java.util.ArrayList.writeObject(ArrayList.java:570) [:1.6.0_26]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_26]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_26]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_26]
at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_26]
at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945) [:1.6.0_26]
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1469) [:1.6.0_26]
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400) [:1.6.0_26]
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158) [:1.6.0_26]
at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1346) [:1.6.0_26]
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1154) [:1.6.0_26]
at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1346) [:1.6.0_26]
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1154) [:1.6.0_26]
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330) [:1.6.0_26]
at java.util.HashMap.writeObject(HashMap.java:1001) [:1.6.0_26]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_26]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_26]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_26]
at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_26]
at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945) [:1.6.0_26]
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1469) [:1.6.0_26]
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400) [:1.6.0_26]
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158) [:1.6.0_26]
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330) [:1.6.0_26]
at com.sun.faces.renderkit.ClientSideStateHelper.doWriteState(ClientSideStateHelper.java:325) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT]
at com.sun.faces.renderkit.ClientSideStateHelper.writeState(ClientSideStateHelper.java:169) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT]
at com.sun.faces.renderkit.ResponseStateManagerImpl.getViewState(ResponseStateManagerImpl.java:135) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT]
... 28 more
{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, 11 months
[JBoss JIRA] (RF-11656) Nested collapsibleSubTable always expanded
by Jesper Vrelits (Created) (JIRA)
Nested collapsibleSubTable always expanded
------------------------------------------
Key: RF-11656
URL: https://issues.jboss.org/browse/RF-11656
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component
Affects Versions: 4.1.0.Milestone3
Reporter: Jesper Vrelits
When I use nested collapsibleSubTable the nested collapsibleSubTable is always expanded.
Even if I put expended="#{false}" it is also expanded.
My facelet looks like this:
{code}
<rich:collapsibleSubTable value="#{logicalInstanceListController.getGroups(environment.entry)}" var="group"
id="envtoggle" expandMode="ajax" expanded="#{environment.expanded}">
<rich:column>
<f:facet name="header">
<h:outputText value="#{dps_msgs['instancegroup']}"/>
</f:facet>
<h:outputText style="margin-left: 15px" value="#{group.entry.name}"/>
<rich:collapsibleSubTableToggler for="logicaltoggle"/>
</rich:column>
<rich:column>
<f:facet name="header">
<h:outputText value="#{dps_msgs['description']}"/>
</f:facet>
<h:outputText value="#{group.entry.description}"/>
</rich:column>
<rich:collapsibleSubTable value="#{logicalInstanceListController.getLogicalInstances(group)}"
var="logicalinstance" id="logicaltoggle" expandMode="ajax"
expanded="#{group.expanded}">
<rich:column>
<h:outputText style="margin-left: 30px" value="#{logicalinstance.name}"/>
</rich:column>
<rich:column>
<h:outputText value="#{logicalinstance.description}"/>
</rich:column>
</rich:collapsibleSubTable>
</rich:collapsibleSubTable>
{code}
Group.expanded seems to be updated correctly, so it seems the Renderer does not use this. A guess is that it uses the parent collapsibleSubTable expanded value, because they seem synchronized. My guess it the Renderer code does not work with nested collapsible sub tables.
--
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, 11 months
[JBoss JIRA] (RF-11908) rich:datascroller not scrolling rich:dataGrid
by Todd Gould (JIRA)
Todd Gould created RF-11908:
-------------------------------
Summary: rich:datascroller not scrolling rich:dataGrid
Key: RF-11908
URL: https://issues.jboss.org/browse/RF-11908
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component
Affects Versions: 3.3.3.Final
Environment: Windows OS in JBoss 5.1
Reporter: Todd Gould
The rich:dataScroller does not work with the rich:dataGrid component. The datascroller represents the proper number of pages for the data in the dataGrid. However, when I select any of the datascroller controlls, the ajax request processes (as witnessed via the associated status), but the dataGrid remains on the first page. Nothing seems to be able to make it progress to another page. No ajax or other errors are generated and all appears to function well except that the datGrid does not scroll.
--
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, 11 months