[JBoss JIRA] Created: (RF-11052) Module components cannot be build with Maven 3
by Pavol Pitonak (JIRA)
Module components cannot be build with Maven 3
----------------------------------------------
Key: RF-11052
URL: https://issues.jboss.org/browse/RF-11052
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.0.0.Final
Environment: RichFaces 4.1.0-SNAPSHOT
Maven 3.0.3
Reporter: Pavol Pitonak
# Clone Git repository https://github.com/richfaces/components.git
# run mvn clean package using Maven 3.0.3
result:
{quote}
[INFO] ------------------------------------------------------------------------
[INFO] Building Richfaces UI Components API 4.1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
...
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3.449s
[INFO] Finished at: Mon Jun 06 15:39:44 CEST 2011
[INFO] Final Memory: 8M/105M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-shade-plugin:1.3.3:shade (default) on project richfaces-components-api: Error creating shaded jar: 1 problem was encountered while building the effective model for org.richfaces.ui:richfaces-components-api:4.1.0-SNAPSHOT
[ERROR] [FATAL] Non-resolvable parent POM for org.richfaces:richfaces-bom:4.1.0-SNAPSHOT: Could not find artifact org.richfaces:richfaces-parent:pom:10 in central (http://repo1.maven.org/maven2) and 'parent.relativePath' points at wrong local POM @ org.richfaces:richfaces-bom:4.1.0-SNAPSHOT, /data/eclipse-workspace/richfaces/build/bom/pom.xml, line 24, column 13
[ERROR] for project org.richfaces.ui:richfaces-components-api:4.1.0-SNAPSHOT at /data/eclipse-workspace/richfaces/components/dist/richfaces-components-api/dependency-reduced-pom.xml for project org.richfaces.ui:richfaces-components-api:4.1.0-SNAPSHOT at /data/eclipse-workspace/richfaces/components/dist/richfaces-components-api/dependency-reduced-pom.xml
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
{quote}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 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
13 years, 6 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
13 years, 6 months
[JBoss JIRA] Created: (RF-10755) managed-bean in richfaces-core-impl
by Martin Kočí (JIRA)
managed-bean in richfaces-core-impl
-----------------------------------
Key: RF-10755
URL: https://issues.jboss.org/browse/RF-10755
Project: RichFaces
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: compatibility
Affects Versions: 4.0.0.CR1
Environment: Richfaces 4.0.0 branch
Reporter: Martin Kočí
richfaces-core-impl contains three definitions of managed-beans:
a4j
a4jSkin
richSkin
By mistake one of our coders created CDI bean named "richSkin" and that caused malfunction of richfaces skinning.
Suggestion: do not provide those beans but implement them as implicit object (similar like JSF implicit object "view" or "sessionScope")
There is SkinPropertiesELResolver already, all what needs to be done is define new implicit object "richSkin" and handle it there in similar way how JSF impl handle implicit objects.
a4jSkin managed-bean seems to be obsolete, about a4j(VerionBean) I'm not sure.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] Created: (RF-10748) CLONE - Extended dataTable. Header scrolled badly on TAB button.
by Ilya Shaikovsky (JIRA)
CLONE - Extended dataTable. Header scrolled badly on TAB button.
----------------------------------------------------------------
Key: RF-10748
URL: https://issues.jboss.org/browse/RF-10748
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-ScrollableDataTable
Affects Versions: 3.2.0
Environment: FF 2.0.0.6
Reporter: Ilya Shaikovsky
Assignee: Konstantin Mishin
Fix For: 3.Future
Attachments: case - 1.png, case - 2.png
Two use-cases failed:
"case - 1.png"
frozenColCount=0
all the columns with inputs
last columns aren't in visible part
When I use TAB key - columns scrolled to be displayed (good) but headers jsut stays (Wrong!)
"case - 2.png"
frozenColCount=2
all the columns with inputs
last columns aren't in visible part
I use TAB key. Focused inputs changed one by one only in "frozen zone" (seems good), but after I press TAB on the last input - the focus jumps to non frozen column input and frozen columns - scrolled and shifted down(Wrong!). But headers still aren't scrolled (good in this case).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months