• Post Reply Bookmark Topic Watch Topic
  • New Topic

migration from mojarra to MyFaces  RSS feed

 
Maurice Le Chat
Greenhorn
Posts: 18
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have a JEE application running well on Glassfish using JSF2 based on Mojarra. This application shall run on WebSphere8, hence must be prorted. WAS does support MyFaces, but support of mojarra is very poor. So, Mojarra has been kicked out and the application references the ibm myFaces jar. On running the application and calling managedBean methods, MethodNotFounExceptions are thrown. e.g.
javax.el.MethodNotFoundException: /resources/utils/formEditingMenu.xhtml at line 39 and column 39 action="#{cc.attrs.handler.generateDocument('HTML')}": Method not found: ch.commcity.monterosa.web.ProjectHandler@43bda4c.generateDocument()
at org.apache.myfaces.view.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:91)
Of course the method exist, as it works perfectly with Glassfish and Mojarra!
Strange is the number between handler and Method ch.commcity.monterosa.web.ProjectHandler@43bda4c.generateDocument() of course the existing method is rather ch.commcity.monterosa.web.ProjectHandler.generateDocument()!
From where this @number is comming?
What configuration may be missing to make it work?
Are the differencies between the 2 JSF2 Implementations really so big?
What could be the reason of the MethodNotFoundExceptio?
Any hint is very apreciated.
 
Tim Holloway
Bartender
Posts: 18531
61
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I believe that @43bda4c indicates an anonymous inner class. It's likely that you have an out-of-date copy of the monterosa web projecthandler class in your classpath.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!