my dog learned polymorphism*
The moose likes JSF and the fly likes Unable to create managed bean. Hello world app. Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of OCM Java EE 6 Enterprise Architect Exam Guide this week in the OCMJEA forum!
JavaRanch » Java Forums » Java » JSF
Bookmark "Unable to create managed bean. Hello world app." Watch "Unable to create managed bean. Hello world app." New topic
Author

Unable to create managed bean. Hello world app.

Dmitry Pidd
Greenhorn

Joined: Jan 13, 2011
Posts: 7
Did several tutorials and all works fine but this hello world example...


Tomcat Exception


index.xhtml


welcome.xhtml


UserBean.java



And faces-config.xml



[Thumbnail for Screen Shot 2012-01-24 at 12.05.49 AM.png]

Tim Holloway
Saloon Keeper

Joined: Jun 25, 2001
Posts: 16022
    
  20

Don't put UserBean in the default package. Use of the default package is generally discouraged, and some IDEs will even yell at you for using it at all.

Oh, and welcome to the Ranch!


Customer surveys are for companies who didn't pay proper attention to begin with.
Dmitry Pidd
Greenhorn

Joined: Jan 13, 2011
Posts: 7
oh no I tried and tried, and with glassfish and modifying faces-config in a lot of ways,- still doesn't work and it drives me crazy.
I just did put it in com.beans.UserBean and changed faces-config accordingly


javax.servlet.ServletException: Unable to create managed bean user. The following problems were found:
- Bean or property class com.beans.UserBean for managed bean user cannot be found.
javax.faces.webapp.FacesServlet.service(FacesServlet.java:606)


Could my user libraries be a problem?


[Thumbnail for Screen Shot 2012-01-24 at 10.00.36 AM.png]

Tim Holloway
Saloon Keeper

Joined: Jun 25, 2001
Posts: 16022
    
  20

The fact that you got a JSF message means that you did almost everything right. Most people don't get that far on the first try.

I did notice one strange thing:



I don't think that that can even compile considering you didn't list any interface names after "implements". And since JSF backing beans are POJOs, there's no requirement to implement any interfaces anyway.

It doesn't hurt to include a no-argument public constructor on your bean, since "proper" POJOs should. But JSF doesn't require it, especially if you don't have any construction-time code to execute.
Dmitry Pidd
Greenhorn

Joined: Jan 13, 2011
Posts: 7
Yes with default constructor it worked!! Thank you I spent about 5 hrs, on it. But why it didn't work before then, if bean is POJO?

sorry for implements, I tried Serrializable just to see if it could be a problem and forgot to delete it
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Unable to create managed bean. Hello world app.