[
http://jira.jboss.com/jira/browse/RF-1713?page=all ]
Bram Biesbrouck resolved RF-1713.
---------------------------------
Resolution: Done
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)
RichFaces 'double implementation' MethodNotFoundException
bug
-------------------------------------------------------------
Key: RF-1713
URL:
http://jira.jboss.com/jira/browse/RF-1713
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.0
Environment: Linux, Jboss AS 4.2.2, Seam 2.0.0 GA
Reporter: Bram Biesbrouck
Assigned To: Sergey Halipov
Fix For: 3.2.0
Attachments: dummy.ear, dummy.zip
When I use "adviseNodeOpened" in a rich:tree component, I end up with a
javax.faces.el.MethodNotFoundException:
adviseNodeOpened="#{fileSystemManager.adviseFileSystemTreeNodeOpened}": Method
not found:
FileSystemManagerImpl:3j011-9i11xv-faathdgv-1-faauxftc-h.adviseFileSystemTreeNodeOpened(org.richfaces.component.UITree)
The former solution was to set UseJBossWebLoader to true, but this breaks the Seam Mail
functionality.
The new solution came when RichFaces impl and api were splitted, but nothing changed with
"adviseNodeOpened"
In the Wiki-example build.xml, I'm seeing this comment:
<!-- Still need the * on richfaces due to bug in version mapper -->
Could this be the reason (the fact that we can't split out the api in the war file
just yet) for this exception to be thrown?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira