Eclipse Community Forums: JavaServer Faces » Why needs to have a MetaDataModelManager per project?

Help

Home

Home » Eclipse Projects » JavaServer Faces » Why needs to have a MetaDataModelManager per project?

Show: Today's Messages :: Show Polls :: Message Navigator

Why needs to have a MetaDataModelManager per project? [message #615741]

Wed, 05 December 2007 16:37

Xiaonan Jiang

Messages: 14
Registered: July 2009

Junior Member

org.eclipse.jst.jsf.common.metadata.internal.MetaDataModelMa nager is a
"singleton instance for each IProject used to manage all standard metadata
models for that project."

This seems imply different projects may have different metadata. How could
this happen?

Thanks.

Report message to a moderator

Previous Topic:	Beans accessing other beans
Next Topic:	Why needs to have a MetaDataModelManager per project?

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 19 22:35:45 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter