JspParseException: TLD file under JAR's META-INF not found

[Former Member]

I have succesully deployed an external generated WAR file using the Developer Studio 'Deploy View'. However, I get an exception at runtime:

javax.servlet.ServletException: Error in parsing the taglib tag in the JSP page. Cannot resolve URI: [http://www.esri.com/adf/web].

at javax.faces.webapp.FacesServlet.service(FacesServlet.java:256)

This URI is defined in a TLD file which is embeded in the META-INF of a JAR which is located in WEB-INF/lib of the WAR file.

This same exact WAR file deploys fine in Tomcat.

I tried doing this in the J2EE 1.4 Preview and it was the same behavior.

How do we fix this?

Enrique

[Former Member]

Hi Enrique Yaptenco

Better to define the taglib url in web.xml file. Also I am not sure but its look like version incompatablity.

Netweaver is using jsp2.1. and may be u develop ur application with ID using jsp2.0.

Thank you

Syed Saifuddin

[Former Member]

Hello everybody

I,ve the same problem when I try to deploy a jsf application that uses Esri tags.

The war work fine In a Tomcat but when I deploy the application in the WAS 5 I get the error Error in parsing the taglib tag in the JSP page. Cannot resolve URI: [http://www.esri.com/adf/web].

I think there aren't problems with the TLD because the proyect runs fine in other environment. It seems like the WAS wasn't able to connect with the URI.

Do you know any solution ?

Thank in advance.

Fernando

[former_member185706]

Hi Fernando,

as was written above, the tld doesn't pass XML validation.

Could you post it here, to see what is wrong?

Regards

Bojidar

[NikiD]

Hello,

a reason for not resolving the URI can be that the TLD is a non-valid xml document. Could you please check with some xml validator that the tld is a valid xml doc?

Best Regards

Nikolai Dokovski

[Former Member]

Hi Nikolai,

It seems you are right, the XML is not valid per http://www.w3.org/2001/03/webdata/xsv

Enrique

[NikiD]

Hi Enrique,

Well then you should try fixing the tld and redeploy the application. That should lead to building a correct taglib map for the application.

Nikolai