Custom taglib and inexplicable jsp compilation issue

Question

Can someone explain what could possibly be happening here? I have been working on this for two days to no avail.
With the following configuration, my jsp behaves as I expect it to on Tomcat, but fails to compile both for Jetty and the Maven2 jspc plugin
deepfij.tld
<taglib version="2.0" xmlns="http://java.sun.com/xml/ns/j2ee [3]" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee web-jsptaglibrary_2_0.xsd">
<tlib-version>1.0</tlib-version>
<short-name>deepfij</short-name>
<uri>com.fijimf.deepfij</uri>
<tag>
<name>menuItem</name>
<tag-class>com.fijimf.deepfij.web.tag.MenuItemTag</tag-class>
<body-content>scriptless</body-content>
<attribute>
<name>item</name>
<required>false</required>
<rtexprvalue>true</rtexprvalue>
</attribute>
</tag>
</taglib>
menubar.jsp
<%@ taglib prefix="df" uri="/WEB-INF/tlds/deepfij.tld"%>
<c:forEach var="page" items="${menuRootPages}">
<df:menuItem item="${page}" />  
</c:forEach>
MenuItemTag.java
package com.fijimf.deepfij.web.tag;
.With the error: com.fijimf.deepfij.web.tag cannot be resolved to a type.
BUT*, if I move MenuItemTag into the package com.fijimf.web, and correspondingly change the .tld, everything works as expected.
Is this a bug, or is there a constraint in taglib packages I don't know about?
Any guidance would be great, because I'd like to put classes where I want them.

Answer 1

This is most likely a bug on the server. The JSP formatted Tag Files usually have a .tag extension on them ( [see tutorial|http://java.sun.com/javaee/5/docs/tutorial/doc/bnama.html] ). The server is probably looking at yyy.xxx.tag and trying to use it as if it was a Tag File named xxx.tag, rather than a package.