javax.faces.el.MethodNotFoundException /view/schema.xhtml @

[grainsan]

<rich:tabPanel switchType="server" id="productPanel"
binding="#{listFeature.currentProduct}"
valueChangeListener="#{listFeature.setCFeature}">

When we using Richface3.1.0 and then got this error. Do anyone know how to resolve this issue?

[grainsan]

Detail error info:
javax.faces.el.MethodNotFoundException: /view/schemaSettings.xhtml @84,52 valueChangeListener="#{listFeature.setCFeature}": Method not found: [e-mail]()
at com.sun.facelets.el.LegacyMethodBinding.invoke(LegacyMethodBinding.java:71)
at javax.faces.component.UIInput.broadcast(UIInput.java:244)
at org.richfaces.component.UISwitchablePanel.broadcast(UISwitchablePanel.java:130)
at org.ajax4jsf.component.AjaxViewRoot.processEvents(AjaxViewRoot.java:186)
at org.ajax4jsf.component.AjaxViewRoot.broadcastEvents(AjaxViewRoot.java:162)
at org.ajax4jsf.component.AjaxViewRoot.processUpdates(AjaxViewRoot.java:311)
......

[rhardy5014]

I am getting a similar problem when trying to call a valueChangeListener when switching tabs in ajax mode.

I get:

13:47:32,463 WARN [lifecycle] /faceletsdefs/messageDetailsOutlook/messageDetails.xhtml @21,63 valueChangeListener="#{tabManager.tabValueChanged}": Method not found: TabManagerBean:5c4o6k2f-lpk3ef-f6sykqaz-1-f6t9djnk-51.tabValueChanged()

tabManager is a Seam Stateful Session Bean.

This occurs with RichFaces 3.1.0, and Seam 1.2.1GA. It all used to work with RichFaces 3.0.1

Richard.

[sergeysmirnov]

If anything (method, class etc) in not found, it is a primary and strong reason to find our why two different versions of the same product are loaded and work together

[rhardy5014]

Sergey,
I am not sure what you mean by

two different versions of the same product are loaded and work together

What I meant was that my code used to work with Rich Faces 3.0.1 but when I migrated to 3.1.0 it no longer works.

I do not have two different versions of the same product loaded at the same time.

Richard.

[maksimkaszynski]

Plz provide code of tabmanager bean - maybe it has wrong signature?