[mermit]

We have a Java project that is essentially a taglib project with taglib jaba sources in src and taglib.tld in src/META-INF directory. MyEclipse Web Projects can pick up the taglib.tld from within the packaged jar but only if the library physically resides in the WEB-INF/lib directory of the web project. I would like to add the taglib java project as a dependency to the the web project and have myeclipse pick the taglib.tld from the dependent java project and have jsp content assist work for jsp’s.

The above works at runtime. I’ve added the taglib project as a dependency to the web project and when myeclipse packages the WAR the taglibproject.jar is put into the WEB-INF/lib directory and tomcat finds the taglib.tld fine. Why not extend myeclipse so that this works also at dev time?

* Janne Kario

[Riyad Kalla]

Janne,
I am surprised that this is the first time someone has requested it, it is an excellent request, I will file it right away.

[Riyad Kalla]

Janne,
After some more investigation one of the developers let me know that this is infact already support, but it is transparent, you don’t have to do anything fancy to get it. Just create a normal Java Project, and under the source folder crweate a META-INF dir, with your TLD file in it. Then for your web project, set the Java Project as a dependency, and optioanlly turn on Smart deployment, and you will get autocomplete and validation in your JSP pages for your taglib.

If your problem is that your TLD seems to come out of sync with the autocomplete, that is a known issue, you just need to either close and reopen the project or restart MyEclipse to dumb it’s taglib cache.

[Author]

Posts