| Author |
Unable to create managed bean. Hello world app.
|
Dmitry Pidd
Greenhorn
Joined: Jan 13, 2011
Posts: 4
|
|
Did several tutorials and all works fine but this hello world example...
Tomcat Exception
index.xhtml
welcome.xhtml
UserBean.java
And faces-config.xml
|
| Filename |
Screen Shot 2012-01-24 at 12.05.49 AM.png |
Download
|
| Description |
|
| Filesize |
46 Kbytes
|
| Downloaded: |
6 time(s) |
|
 |
Tim Holloway
Saloon Keeper
Joined: Jun 25, 2001
Posts: 12513
|
|
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!
|
One of the most odious afflictions that Business has inflicted on the modern English language is "pro-active". Most of the time it's simply redundantly used in place of the simple old word "active". And a good deal of the rest of the time it means "You're not overworked enough yet, so go out and find more!"
|
 |
Dmitry Pidd
Greenhorn
Joined: Jan 13, 2011
Posts: 4
|
|
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?
|
| Filename |
Screen Shot 2012-01-24 at 10.00.36 AM.png |
Download
|
| Description |
|
| Filesize |
57 Kbytes
|
| Downloaded: |
1 time(s) |
|
 |
Tim Holloway
Saloon Keeper
Joined: Jun 25, 2001
Posts: 12513
|
|
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: 4
|
|
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
|
 |
 |
|
|
subject: Unable to create managed bean. Hello world app.
|
|
|