This week's book giveaway is in the OO, Patterns, UML and Refactoring forum.
We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line!
See this thread for details.
The moose likes JSF and the fly likes JSF2.0 WARNING: JSF1074 Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

JavaRanch » Java Forums » Java » JSF
Bookmark "JSF2.0 WARNING: JSF1074" Watch "JSF2.0 WARNING: JSF1074" New topic


Mitchell Smith

Joined: Aug 30, 2011
Posts: 2

When starting my web-app i see lots of Warnings as below

I understand that these are caused by duplicated definitions for managed-beans of the name.

My Question is... The Warning states Replacing existing managed bean class type, are any managed-property definitions from the first of the managed bean definition still created. Or is the entire definition for the managed-bean and all it managed properties cleared and overwritten?

Tim Holloway
Saloon Keeper

Joined: Jun 25, 2001
Posts: 17011

The registration process is simply a name/value binding. For example, if the ManagedBean is in session scope, then the actual result will end up being that the J2EE HttpSession object's "setAttribute" method will be invoked to bind the name to the managed object.

If you define a managed bean and bind it to a name, then bind another bean to the same name, the first bean goes out of scope just as it would if you had invoked setAttribute manually.

Although if you're trying to use the same name for more than one object, you have a serious design problem anyway.

Customer surveys are for companies who didn't pay proper attention to begin with.
Have you checked out Aspose?
subject: JSF2.0 WARNING: JSF1074
It's not a secret anymore!