This question actually involves a couple different technologies in addition to JSF but hopefully this is the best forum to pose it:
I've built a portlet using JSF that is using Hibernate to persist data back to the Liferay Database. I used Liferay's Service Builder to create my persistence classes and bundled them in a .jar which I places in my tomcat/lib/ext folder.
I'm calling the code from my backing bean thus:
And my FeedbackItemLocalServiceImpl addFeebackItem method is written to accept a single String parameter.
I'm getting the following error on the page when I click my form submit button:
SEVERE: org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'org.ea.portal.feedback.service.FeedbackItemLocalServiceUtil' is defined
javax.faces.el.EvaluationException: org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'org.ea.portal.feedback.service.FeedbackItemLocalServiceUtil' is defined
So it looks like the EL is trying to find this bean but I don't understand why. It's not a managed bean, the methods in it are all static, and I'm not referencing it in any view code.
The way I read it, your FeedBackLocalItemServiceUtil class is asking LifeRay for a bean whose name is "org.ea.portal.feedback.service.FeedbackItemLocalServiceUtil".
While that's legal as a bean name, it's more likely that you have your bean names and class names reversed in one of your Spring configuration definitions.
Adding to the confusion is why a FeedBackLocalItemServiceUtil would be asking a service locator for a bean whose name is "FeedBackLocalItemServiceUtil" (to abbreviate it). Kind of looking for oneself, no?
In any event, it doesn't appear that you've included the source code where the actual failure occurs, so I've had to guess. Although it may ultimately not be the code that's wrong, since it looks more like an issue with the Spring config file. Or annotation, if that's what you're using.
Customer surveys are for companies who didn't pay proper attention to begin with.
The Spring config was auto-generated by the Liferay Service Builder so I haven't looked at it yet, but that sounds like a good place to check. If there's no problem there and I still can't resolve it, I'll post the more relevant source code here.