This content has been marked as final.
Show 3 replies
-
1. Re: old RichFaces bug: MethodNotFoundException back?
pmuir Dec 20, 2007 6:16 AM (in response to beligum)Make sure to report this in the RichFaces forum or JIRA.
-
2. Re: old RichFaces bug: MethodNotFoundException back?
beligum Jan 28, 2008 12:24 PM (in response to beligum)Did some more work on this:
When (in the bean), I use this function:public Boolean adviseFileSystemTreeNodeOpened(UITree tree) { Inode inode = ((FileSystemTreeNode)tree.getRowData()).getInode(); if (this.getSelectedSpaceMember()!=null) { return inode.hasAsChild(this.getSelectedSpaceMember().getInode()); } return null; }
The compiler complains about the fact that tree.getRowData() is not specified in richfaces.api (but in richfaces.impl), which may be the reason why we can't split impl and api. Note that I'm using rich:recursiveTreeNodesAdaptor, so I'm forced to use getRowData() instead of getTreeNode() (which is in richfaces.api).
Any comments plz?
b.
ps: jira-link: http://jira.jboss.org/jira/browse/RF-1713 -
3. Re: old RichFaces bug: MethodNotFoundException back?
beligum Feb 1, 2008 8:43 AM (in response to beligum)I found the fix for this:
add jboss-web.xml to the web context with a seperate classloader:<class-loading java2ClassLoadingCompliance="false"> <loader-repository> seam.jboss.org:loader=<your-app-name> <loader-repository-config>java2ParentDelegation=false</loader-repository-config> </loader-repository> </class-loading>
and add the richfaces-impl.jar to the ejb context (richfaces-api.jar and richfaces-ui.jar go into the root ear context)