|Re: HELP: Does WTP have a way to extend the TLD loading [message #550043 is a reply to message #549514]
||Wed, 28 July 2010 20:29
| Nitin Dahyabhai
Registered: July 2009
On 7/26/2010 10:16 PM, Jack wrote:|
> Actually, maybe sounds strange, we do not depend on the tld file.
> The tag lib instance will be generated in memory at runtime, then the
> tags in jsp can be resolved correctly. Runtime will get tag info from
> classes instead of from tld file.
> But for editor tool, we need tld to support validation and code completion.
I'm not sure this is going to be possible. In addition to resolving the
taglib URI in the JSP, we actually need to read the .tld or .tag/.tagx
file to know about the tags inside of it, and that information's
expected to be expressed in classes and interfaces that aren't API (the
TaglibIndex and ProjectDescription are locked down and inaccessible as
much as possible because of potential threading issues and for
performance. While it's possible to inject awareness of the tags
themselves in a similar way as is done for JSF Facelets, using the
provisional org.eclipse.wst.xml.core.modelQueryExtensions extension
point, it still wouldn't remove the validation messages in the taglib
Eclipse WTP Source Editing and JSDT
Powered by FUDForum
. Page generated in 0.02824 seconds