Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » JavaServer Faces » Why needs to have a MetaDataModelManager per project?
Why needs to have a MetaDataModelManager per project? [message #475345] Wed, 05 December 2007 11:37 Go to next message
Xiaonan Jiang is currently offline 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.
Re: Why needs to have a MetaDataModelManager per project? [message #475346 is a reply to message #475345] Wed, 05 December 2007 16:46 Go to previous message
Cameron Bateman is currently offline Cameron Bateman
Messages: 480
Registered: July 2009
Senior Member
> This seems imply different projects may have different metadata. How could
> this happen?

Yes, this situation is possible because some metadata is loaded or derived
based on the contents of a project or it's classpath.

For example:

1) JSP TLD library meta-data is generally found in META-INF/*.tld of the
contributing jar file. Those jar files are found by searching a project's
classpath.

2) Component meta-data can be embedded in faces-config files (although we
currently don't have a loading strategy for this) using the "extension"
elements. These files can be anywhere on the JSF search path including in
the $webroot/META-INF, $webroot/WEB-INF, anywhere specified in the web.xml
as well as in each jar file on the classpath that defines JSF components.


--Cam
Re: Why needs to have a MetaDataModelManager per project? [message #615742 is a reply to message #475345] Wed, 05 December 2007 16:46 Go to previous message
Cameron Bateman is currently offline Cameron Bateman
Messages: 480
Registered: July 2009
Senior Member
> This seems imply different projects may have different metadata. How could
> this happen?

Yes, this situation is possible because some metadata is loaded or derived
based on the contents of a project or it's classpath.

For example:

1) JSP TLD library meta-data is generally found in META-INF/*.tld of the
contributing jar file. Those jar files are found by searching a project's
classpath.

2) Component meta-data can be embedded in faces-config files (although we
currently don't have a loading strategy for this) using the "extension"
elements. These files can be anywhere on the JSF search path including in
the $webroot/META-INF, $webroot/WEB-INF, anywhere specified in the web.xml
as well as in each jar file on the classpath that defines JSF components.


--Cam
Previous Topic:Why needs to have a MetaDataModelManager per project?
Next Topic:hibernate and jsp
Goto Forum:
  


Current Time: Wed Aug 20 06:52:45 EDT 2014

Powered by FUDForum. Page generated in 0.02170 seconds