Win a copy of Think Java: How to Think Like a Computer Scientist this week in the Java in General forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

JSF2.0 WARNING: JSF1074

 
Mitchell Smith
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

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?

Thanks
 
Tim Holloway
Saloon Keeper
Pie
Posts: 18152
52
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic