We are encountering these errors whenever an app is deployed and
initialized on our Oracle Application Servers.

------------------------------------------------------------------
09/01/30 14:17:53 Notification ==> Application Deployer for
portalreports COMPLETES [ 2009-01-30T14:17:53.418EST ]

09/01/30 14:17:53 Initialized log4j with:
/home/oastest/ora_app/test_app01/j2ee/insideMIT-portlets/
applications/commuting-portlets/commuting-portlets/WEB-INF/
classes/log4j.properties

09/01/30 14:17:53 Initialized log4j with:/home/oastest/ora_app/
test_app01/j2ee/insideMIT-portlets/applications/commuting-
portlets/commuting-portlets/WEB-INF/classes/log4j.properties

09/01/30 14:17:53 Error: null
09/01/30 14:17:53 Errors parsing
jar:file:/home/oastest/ora_app/test_app01/j2ee/
insideMIT-portlets/applications/portalreports/
portalreports/WEB-INF/lib/taglibs-standard-1.1.2-3.jar!
/META-INF/fn.tld

09/01/30 14:17:53 Error: null
09/01/30 14:17:53 Errors parsing
jar:file:/home/oastest/ora_app/test_app01/j2ee/
insideMIT-portlets/applications/portalreports/
portalreports/WEB-INF/lib/taglibs-standard-1.1.2-3.jar!
/META-INF/permittedTaglibs.tld

09/01/30 14:17:53 Error: null
09/01/30 14:17:53 Errors parsing
jar:file:/home/oastest/ora_app/test_app01/j2ee/
insideMIT-portlets/applications/portalreports/
portalreports/WEB-INF/lib/taglibs-standard-1.1.2-3.jar!
/META-INF/scriptfree.tld
------------------------------------------------------------------

These parsing errors alway occur for the same tlds:
fn.tld
permittedTaglibs.tld
scriptfree.tld

These tlds DO exist in taglibs-standard-1.1.2-3.jar ; however,
unlike the other tlds in that jar, these 3 tlds do NOT have any
TAG tags.

I am assuming that is the reason for the null error / error
parsing messages.

My question is: Is it legitimate to have a tld without any
TAGs? or is Oracle's OC4J container being too fussy? or
something else?

It does not prevent the application from running, but it would be
nice to know if this is a real problem.

Any ideas?