| RE: [wtp-dev] TLDDocument |
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
-----Original Message-----
From: Nitin Dahyabhai [mailto:nitind@xxxxxxxxxx]
Sent: Wednesday, December 27, 2006 10:59 AM
To: wtp-dev@xxxxxxxxxxx
Cc: gerry.kessler@xxxxxxxxxx
Subject: Re: [wtp-dev] TLDDocument
Gerry,
Simply put, no, not really. org.eclipse.jst.jsp.core.internal.contentmodel.tld.CMDocumentFactoryTLD.createCMDocument(ITaglibRecord) returns the corresponding TLDDocument for an ITaglibRecord, and is the method used within the JSP model itself. It's internal as well, though, and the TLDDocument and related interfaces will probably remain internal unless the XML content model interfaces become API first.
Could you tell me what information you're looking for in the TLDDocument? A lot of the surface details are available through the ITaglibRecord's descriptor object already, and I'd rather we pursue keeping the JSP and JSF plugins API clean as much as possible.
---
Nitin Dahyabhai
Structured Source Editing
"Gerry Kessler" <gerry.kessler@xxxxxxxxxx>
Sent by: wtp-dev-bounces@xxxxxxxxxxx12/26/2006 06:56 PM
"gerry.kessler@xxxxxxxxxx" <gerry.kessler@xxxxxxxxxx>; Please respond to
"General discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>
"wtp-dev@xxxxxxxxxxx" <wtp-dev@xxxxxxxxxxx> [wtp-dev] TLDDocument
Is there an API to get at a TLDDocument given the cm document uri and a project for context? I can see how to get a ITaglibRecord from the TaglibIndex, but I am not sure how to turn that into the TLDDocument. Everything I see is internal.
Thanks,
Gerry Kessler
WTP JSF Tools Team