Cameron Bateman wrote:
> JSP 2.1 spec section JSP.8.4.2 states:
>
> "JSP 2.0 adds an additional TLD element to describe tags within a tag
> library,
> namely <tag-file>. The <tag-file> element requires <name> and <path>
> subelements ... "
>
> Is there a way to access this information from the TLD API? I thought
> TLDDocument would be the interface that would have it, but there is
> nothing apparent.

org.eclipse.jst.jsp.core.internal.contentmodel.tld.provision al.TLDElementDeclaration.getPath()
should contain it as it's specific to the tag.

> Cameron Bateman wrote:
>> Is there a way to access this information from the TLD API? I thought
>> TLDDocument would be the interface that would have it, but there is
>> nothing apparent.

> org.eclipse.jst.jsp.core.internal.contentmodel.tld.provision al.TLDElementDecl
> aration.getPath()
> should contain it as it's specific to the tag.

So the concept of tag and tag-file have been merged for these purposes?
i.e. the tag-file is loaded into a TLDDocument's metadata as though it
were defined in the TLD as opposed to the referenced tag file? Is there
any way to be certain of this i.e. is the path only non-null if it's a
tag-file as opposed to a tag?

Cameron Bateman wrote:
> Nitin Dahyabhai wrote:
> So the concept of tag and tag-file have been merged for these purposes?
> i.e. the tag-file is loaded into a TLDDocument's metadata as though it
> were defined in the TLD as opposed to the referenced tag file? Is there
> any way to be certain of this i.e. is the path only non-null if it's a
> tag-file as opposed to a tag?

It's more along the lines of allowing users of the
TLDElementDeclaration to not have to care whether it came from a tag
file or not. And yes, it will only return a path value when the tag
wasn't solely defined by the .tld, or if there was no .tld file at
all (tagdirs).