• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

I'm confused about variable resolving for JSF 1.2+Spring2.5+Facelets1.1

 
Ranch Hand
Posts: 37
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
In Spring 2.5.x docs I read that for JSF 1.1 configure this resolver in faces-config.xml file as follows:



And all JSF expressions can then implicitly refer to the names of Spring-managed service layer beans, for example in property values of JSF-managed beans:


But I use JSF 1.2 and get this error:
com.sun.faces.mgbean.ManagedBeanCreationException: Unable to set property service for managed bean myJsfManagedBean

When I use this resolver:
<el-resolver>org.springframework.web.jsf.el.SpringBeanFacesELResolver</el-resolver>
I get this warning:
Class org.springframework.web.jsf.el.SpringBeanFacesELResolver must extend the type javax.el.ELResolver
and this error:
javax.faces.el.EvaluationException: java.lang.ClassCastException: java.lang.Long cannot be cast to domain.User


Could any one please help me?
 
Saloon Keeper
Posts: 27882
197
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I think you did it right the first time, but you probably didn't define a public setter named "setService" in MyJsfManagedBean with the proper parameter type. It's one of my most ocmmon JSF mistakes. Fortunately, it's easily corrected.
reply
    Bookmark Topic Watch Topic
  • New Topic