[JBoss JIRA] Created: (RF-11166) menuGroup does not expand when added programatically
by Riccardo Pasquini (JIRA)
menuGroup does not expand when added programatically
----------------------------------------------------
Key: RF-11166
URL: https://issues.jboss.org/browse/RF-11166
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-menu
Affects Versions: 4.0.0.Final
Environment: java version "1.6.0_26"
opensuse 11.4 kernel 2.6.37.6-0.7-desktop x86_64
Jboss 7
Reporter: Riccardo Pasquini
toolbarGroup bound to a session scoped bean, dropdown menus are added programmatically
these dropdown menus contains both menuitems and menugroups and so on...
first level of menugroups is rendered but not expanded on mouse over
no other menugroups are in any other part of the page, the toolbar is in a form
the java part seems to be ok because it remains unchanged in the working workaround description
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] Created: (RF-11162) dynamically-enabled commandButton doesn't work (need a:htmlCommandButton?)
by Tom Bryan (JIRA)
dynamically-enabled commandButton doesn't work (need a:htmlCommandButton?)
--------------------------------------------------------------------------
Key: RF-11162
URL: https://issues.jboss.org/browse/RF-11162
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 3.3.1
Environment: Seam 2.2.0.GA, Richfaces 3.3.1, and JBoss 5.1.0
Reporter: Tom Bryan
When an h:commandButton is initially rendered as disabled and then dynamically-enabled during an a:commandButton, it does not seem to submit the page. Changing the h:commandButton to a h:commandLink gives the same results, but changing it to an a:htmlCommandLink does work. I'm not sure whether h:commandButton is supposed to work in this case or whether there should just be an a:htmlCommandButton.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] Created: (RF-11145) Validation for initial unrendered input fields fails
by Mano Swerts (JIRA)
Validation for initial unrendered input fields fails
-----------------------------------------------------
Key: RF-11145
URL: https://issues.jboss.org/browse/RF-11145
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-validators
Affects Versions: 4.1.0.Final
Environment: Tomcat 7, JSF 2.0, Spring, Hibernate
Reporter: Mano Swerts
We have some input fields with validation on them, that are NOT rendered on initial page load. When we hit a button, the input fields are rendered but the client side validation functions and cvs library are not loaded onto the page. We think this is a bug. Could you please look into this.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] Created: (RF-11102) NullPointerException in rich:tree node selection
by u j (JIRA)
NullPointerException in rich:tree node selection
------------------------------------------------
Key: RF-11102
URL: https://issues.jboss.org/browse/RF-11102
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-tree
Affects Versions: 4.0.0.Final
Reporter: u j
In a tree selection listener method I update the tree itself and get a nullpointerexception afterwards:
18:43:37,156 SEVERE [org.richfaces.log.Context] null: java.lang.NullPointerException
at org.richfaces.model.ClassicTreeNodeDataModelImpl.setupChildContext(ClassicTreeNodeDataModelImpl.java:49) [:4.0.0-SNAPSHOT]
at org.richfaces.model.ClassicTreeNodeDataModelImpl.setupChildContext(ClassicTreeNodeDataModelImpl.java:35) [:4.0.0-SNAPSHOT]
at org.richfaces.model.NodesTreeSequenceKeyModel.setupKey(NodesTreeSequenceKeyModel.java:47) [:4.0.0-SNAPSHOT]
at org.richfaces.model.TreeSequenceKeyModel.setRowKey(TreeSequenceKeyModel.java:49) [:4.0.0-SNAPSHOT]
at org.richfaces.component.UIDataAdaptor.setRowKey(UIDataAdaptor.java:277) [:]
at org.richfaces.renderkit.TreeRendererBase.encodeSelectionStateInput(TreeRendererBase.java:131) [:4.0.0-SNAPSHOT]
at org.richfaces.renderkit.html.TreeRenderer.encodeEnd(TreeRenderer.java:145) [:4.0.0-SNAPSHOT]
at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:875) [:2.1.1-FCS]
at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1763) [:2.1.1-FCS]
at org.richfaces.context.ExtendedPartialViewContextImpl$RenderVisitCallback.visit(ExtendedPartialViewContextImpl.java:514) [:4.0.0-SNAPSHOT]
at org.richfaces.context.BaseExtendedVisitContext.invokeVisitCallback(BaseExtendedVisitContext.java:337) [:4.0.0-SNAPSHOT]
at org.richfaces.component.UIDataAdaptor.visitTree(UIDataAdaptor.java:1235) [:]
at javax.faces.component.UIComponent.visitTree(UIComponent.java:1600) [:2.1.1-FCS]
at javax.faces.component.UIComponent.visitTree(UIComponent.java:1600) [:2.1.1-FCS]
at javax.faces.component.UIComponent.visitTree(UIComponent.java:1600) [:2.1.1-FCS]
at javax.faces.component.UIForm.visitTree(UIForm.java:335) [:2.1.1-FCS]
at javax.faces.component.UIComponent.visitTree(UIComponent.java:1600) [:2.1.1-FCS]
at javax.faces.component.UIComponent.visitTree(UIComponent.java:1600) [:2.1.1-FCS]
...
The problem seems to occur when a node is selected which is not present in the new tree.
But the implementation should be so robust that there is no exception.
I do not reassign the bound root node object, instead I remove all child nodes and add the new nodes to the root.
The tree definition is:
<rich:tree value="#{searchBean.suggestTree}" var="node" id="treeSuggest"
nodeClass="com.myapp.web.tree.EstabSuggestTreeNode"
nodeType="#{node.type}" selectionType="ajax"
toggleType="client" render="treeSuggest,detail"
selectionChangeListener="#{searchBean.treeSuggestSelectionChanged}">
<rich:treeNode type="neighborhood">
<h:outputText value="#{node.name}" />
</rich:treeNode>
<rich:treeNode type="estab" >
<h:outputText value="#{node.name}" />
</rich:treeNode>
</rich:tree>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] Updated: (RF-11207) showcase - a4j:outputPanel - echo returns typed text from input, and it should not
by Juraj Huska (JIRA)
[ https://issues.jboss.org/browse/RF-11207?page=com.atlassian.jira.plugin.s... ]
Juraj Huska updated RF-11207:
-----------------------------
Summary: showcase - a4j:outputPanel - echo returns typed text from input, and it should not (was: echo returns typed text from input in the sample for a4j:outputPanel in showcase and it should not)
> showcase - a4j:outputPanel - echo returns typed text from input, and it should not
> ----------------------------------------------------------------------------------
>
> Key: RF-11207
> URL: https://issues.jboss.org/browse/RF-11207
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: showcase
> Affects Versions: 4.1.0.Milestone1
> Environment: richfaces-showcase-4.1.0.20110805-M1-jbas7.war, richfaces-showcase-4.1.0.20110805-M1-jee6.war
> container: jboss-as-7.0.0.Final, jboss-as-6.0.0.Final
> browser Firefox 5.0.1, IE 9
> Reporter: Juraj Huska
> Fix For: 4.1.0.Milestone2
>
> Attachments: outputPanelWrong1.png, outputPanelWrong2.png
>
>
> In the simple sample for a4j:outputPanel in showcase, when typing to the first input something and then pressing enter key, the text from input is echoed and it should not according to the text description of this sample:
> 'This code does not work as expected. The expected echo text does not appear below even the condition for 'rendered' returns true. Also, the error message does not appear when the length of the text reaches the limit. '
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] Created: (RF-11215) FileUpload - when the "Clear All" is on the left side, there is a left margin
by Jan Papousek (JIRA)
FileUpload - when the "Clear All" is on the left side, there is a left margin
-----------------------------------------------------------------------------
Key: RF-11215
URL: https://issues.jboss.org/browse/RF-11215
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Environment: * RichFaces 4.1.0.20110805-M1 r.10246d45dddd1d2aa2034317d5a832394cc919f9
* Metamer 4.1.0.20110805-M1 r.22604
* Mojarra 2.1.3-FCS
* Apache Tomcat 6.0.32
* OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux
* Firefox 3.6.19 @ Linux i686 (x86_64)
Reporter: Jan Papousek
When the attribute *dir* is set to *rtl* and the "Clear All" button is displayed, there is a space on the left side.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months