Hi
Nitin,
In
a nutshell, we would like to be able to access the TLD model directly beyond
the tag file information that I know I can get from
the ITaglibRecord. We have specific interest in
accessing all of the tag and attribute metadata, and I am assuming
for the moment, that TLDDocument would be the way to get to
it.
Why
do we want access? While looking at the Visual Page Designer and the
kinds of metadata that it was needing and using, we saw room for
improvement. The tooling was looking for metadata in multiple places
including the TLD. As metadata becomes more standardized (JSR-273, JSR-276,
etc.), the tooling was going to have even more places to look. From the tooling
perspective, it is highly desireable to perform a single query that would
locate metadata for some entity, if it exists. It is also desirable to isolate
the tooling from changes in the way metadata is provided.
What
we have concieved is a generalized model for metadata with a mechanism for
loading it from multiple sources using a strategy of some kind. For a given
"domain" of metadata, say JSFTags as an example, metadata could
potentially come from a persisted, generalized model file, some
hand-rolled model, JSR-276 metadata, or a TLD. Each source of metadata
can be translated into the domain of metadata that the tool requires so that a
single, merged model of metadata can be queried. At least, this is a very brief
description of what we would like to do .
Is
TLDDocument meant to be provisional API or not? The package it is in
is:
"org.eclipse.jst.jsp.core.internal.contentmodel.tld.provisional". Is
there any way to get directly at information contained by a
TLD? Suggestions?
Thanks,
Gerry
Kessler