[richfaces-issues] [JBoss JIRA] Commented: (RF-1713) RichFaces 'double implementation' MethodNotFoundException bug
[
https://issues.jboss.org/browse/RF-1713?page=com.atlassian.jira.plugin.sy...
]
Nishan Senevirathna commented on RF-1713:
-----------------------------------------
@Kurt Vanlandegem
thanks in advanced for your comment. I can't figure out what you said. please explain
this "and add the richfaces-impl.jar to the ejb context (richfaces-api.jar and
richfaces-ui.jar go into the root ear context)" which was extracted from your
comment.
Thank you
RichFaces 'double implementation' MethodNotFoundException
bug
-------------------------------------------------------------
Key: RF-1713
URL: https://issues.jboss.org/browse/RF-1713
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 3.2.0
Environment: Linux, Jboss AS 4.2.2, Seam 2.0.0 GA
Reporter: Kurt Vanlandegem
Assignee: Aleksej Yanul
Fix For: 3.2.0, 3.2.1
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira