Also corresponging Tomcat issue:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27469

Well, Kin-Man's first fix is not enough to enable this functionality
as Libor found out already. Filed another issue for Tomcat:
http://issues.apache.org/bugzilla/show_bug.cgi?id=32359

*** Issue 51760 has been marked as a duplicate of this issue. ***

<rant>
My experience dealing with the Tomcat folks has been extremely sour in
the past. My 2 cents is never rely on them to do anything on your
behalf. They are too proactive in closing issues as INVALID or WONTFIX
with no good reason.
</rant>

All that goes to say: the less you depend upon them, the better. Also,
I am noticing this issue is over 7 months old... that's not a good sign.

 I really share your experience with SOME (I could name at least two
of them) of the tomcat folks. But, not all of them behave the same
way, and we have always been able to find somebody who's open to new
ideas how to help tomcat users. So I'm not that pesimistic.
 This issue is filed for a long time, but no resources have been given
to it and there were more blocking issues. Current situation is
different - some of the issues were fixed (even though very important
one in tomcat still isn't) and Libor Kotouc has the feature on his
tasklist, so we'll certainly do what we can to make the feature work.
Right, Libor? ;O)

Definitelly :) The independence is nice, but it makes no sense to
implement the mappings inside of NB. It is JSP compiler's job to do it
and we hope that Tomcat's staff will support this feature and we then
bring it to NB users.

Has there been an updated on this issue? On the Tomcat end of things
the issue is closed as "invalid" and they tell us to discuss the
matter on the mailing list, decide on an approach and then reopen the
issue. On our end, it looks like we're waiting for them. So who's
holding up progress here? My experience with .tagx is getting very
frustrating :(

I communicate directly with Kin-Man Chung, he have good experience
with him from the past.

Done.

v