Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Invalid
-
Affects Version/s: 1.6.1
-
Fix Version/s: 1.6.2
-
Component/s: ICE-Components
-
Labels:None
-
Environment:all
-
Support Case References:
-
Workaround Exists:Yes
-
Workaround Description:If no binding is required, you can remove it and the tree will function correctly.
Description
When having both a value and component binding on a tree component, a user will often encounter a 'tree tag requires a single child treeNode tag' exception. The page containing the tree will render correctly the first time, but if a refresh is done on the page, or a simple navigation is done from that page back to itself, the exception will be thrown. I have attached a test case which is our basic tree component along with a simple binding.
-
Hide
-
-
META-INF/MANIFEST.MF
-
WEB-INF/faces-config.xml
-
WEB-INF/web.xml
-
basicTree.jspx
-
index.jsp
-
WEB-INF/classes/com/.../basic/TreeBean.class
-
WEB-INF/classes/com/.../basic/TreeBean.java
-
WEB-INF/lib/jsf-api.jar
-
WEB-INF/lib/jsf-impl.jar
-
WEB-INF/lib/backport-util-concurrent.jar
-
WEB-INF/lib/commons-beanutils.jar
-
WEB-INF/lib/commons-collections.jar
-
WEB-INF/lib/commons-digester.jar
-
WEB-INF/lib/commons-discovery.jar
-
WEB-INF/lib/commons-el.jar
-
WEB-INF/lib/commons-fileupload.jar
-
WEB-INF/lib/commons-logging.jar
-
WEB-INF/lib/jstl.jar
-
WEB-INF/.../krysalis-jCharts-1.0.0-alpha-1.jar
-
WEB-INF/lib/xercesImpl.jar
-
WEB-INF/lib/xml-apis.jar
-
WEB-INF/lib/icefaces.jar
-
WEB-INF/lib/icefaces-comps.jar
-
WEB-INF/lib/el-api.jar
-
WEB-INF/lib/el-ri.jar
-
WEB-INF/lib/icefaces-facelets.jar
-
-
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion