I have often encounter the situation where I want to append a tag to an existing library to avoid having to introduce a new namespace and, as a result, a fine-grained division of tags. However, currently, the mapping is such that you get one tag library per taglib.xml file. More than one taglib.xml, more than one tag library. Would it be possible to have the implementation detect two taglib.xml referencing the same namespace and merge the tags? Obviously, a startup exception would occur if the same tag is declared in more than one file with the same namespace, but I hardly think that would be much of an obstacle to the developer.<br>
<br>To cite a specific use case, we want to have multiple modules in Seam, but we really don't want to have more namespaces than we need. Of course, we could get the build to merge the XML files, but that might not be possible if the developer is deploying the framework as separate JAR files.<br>
<br>-Dan<br clear="all"><br>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br><br><a href="http://mojavelinux.com">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br>
<a href="http://in.relation.to/Bloggers/Dan">http://in.relation.to/Bloggers/Dan</a><br><br>NOTE: While I make a strong effort to keep up with my email on a daily<br>basis, personal or other work matters can sometimes keep me away<br>
from my email. If you contact me, but don't hear back for more than a week,<br>it is very likely that I am excessively backlogged or the message was<br>caught in the spam filters. Please don't hesitate to resend a message if<br>
you feel that it did not reach my attention.<br>