Unable to read TLD "META-INF/c-1_0.tld"

Hi guys,
I'm using Tomcat 5.5.7 and jdk1.5.0_02 installed under Winds XP PRO SP2. I'm also using Standard-1.1: JSTL 1.1 (2.0). But when trying to view the 1st page, Ｉ　ｇｏｔ　ｔｈｅ　ｆｏｌｌｏｗｉｎｇ　ｅｒｒｏｒ　ｍｓｇ：
org.apache.jasper.JasperException: Unable to read TLD "META-INF/c-1_0.tld" from JAR file "file:/C:/Tomcat5/webapps/stufftolet/WEB-INF/lib/standard.jar": org.apache.jasper.JasperException: Failed to load or instantiate TagLibraryValidator class: org.apache.taglibs.standard.tlv.JstlCoreTLV
     org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:50)
     org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:407)
     org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:179)
     org.apache.jasper.compiler.TagLibraryInfoImpl.<init>(TagLibraryInfoImpl.java:181)
     org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:418)
     org.apache.jasper.compiler.Parser.parseDirective(Parser.java:483)
     org.apache.jasper.compiler.Parser.parseElements(Parser.java:1539)
     org.apache.jasper.compiler.Parser.parse(Parser.java:126)
     org.apache.jasper.compiler.ParserController.doParse(ParserController.java:211)
     org.apache.jasper.compiler.ParserController.parse(ParserController.java:100)
     org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:146)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:286)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:267)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:255)
     org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:556)
     org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:296)
     org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
     org.apache.jasper.servlet.JspServlet.service(JspServlet.java:245)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
ｐｌｓ　ｈｅｌｐ．．．．Ｉ　ｒｅａｌｌｙ　ｎｅｅｄ　ｈｅｌｐ　ｄｅｓｐｅｒａｔｅｌｙ　！　Ｔｈａｎｋs !
regards,
kmthien

Hi evnafets,
My index.jsp looks like below:
<%@ taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core" %>
<html>
<head>
          <meta http-equiv="Content-Type" content="text/html;charset=UTF-8"/>
          <meta http-equiv="Pragma" content="no-cache"/>
          <meta http-equiv="Expires" content="-1"/>
          <meta name="Security" content="public"/>
          <meta name="Robots" content="index,follow"/>
          <meta name="Description" content="Stufftolet Index Page."/>
</head>
<body>
<jsp:forward page="selectcountry.jsf"/>
</body>
</html>
and I still got the following error:
org.apache.jasper.JasperException: Unable to read TLD "META-INF/c.tld" from JAR file "file:/C:/Tomcat5/webapps/stufftolet/WEB-INF/lib/standard.jar": org.apache.jasper.JasperException: Failed to load or instantiate TagLibraryValidator class: org.apache.taglibs.standard.tlv.JstlCoreTLV
     org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:50)
     org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:407)
     org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:179)
     org.apache.jasper.compiler.TagLibraryInfoImpl.<init>(TagLibraryInfoImpl.java:181)
     org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:418)
     org.apache.jasper.compiler.Parser.parseDirective(Parser.java:483)
     org.apache.jasper.compiler.Parser.parseElements(Parser.java:1539)
     org.apache.jasper.compiler.Parser.parse(Parser.java:126)
     org.apache.jasper.compiler.ParserController.doParse(ParserController.java:211)
     org.apache.jasper.compiler.ParserController.parse(ParserController.java:100)
     org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:146)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:286)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:267)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:255)
     org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:556)
     org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:296)
     org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
     org.apache.jasper.servlet.JspServlet.service(JspServlet.java:245)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
Appreciate if u could give somemore assistance here, Thanks !

Similar Messages

Unable to read TLD "META-INF/jsf_core.tld

Hi guys,
I have Tomcat 5.5.7 and jdk1.5.0_02 on Windows XP Pro ! I am using jsf-1_1_01. One of my page is as below:
<%@ taglib prefix="f" uri="http://java.sun.com/jsf/core" %>
<%@ taglib prefix="h" uri="http://java.sun.com/jsf/html" %>
<f:loadBundle basename="com.stufftolet.view.bundle.selectcountry" var="msg"/>
<f:view locale="#{catalogBean.currentLocale}">
and I got the following error:
org.apache.jasper.JasperException: Unable to read TLD "META-INF/jsf_core.tld" from JAR file "file:/C:/Tomcat5/webapps/stufftolet/WEB-INF/lib/jsf-impl.jar": org.apache.jasper.JasperException: Failed to load or instantiate TagLibraryValidator class: com.sun.faces.taglib.jsf_core.CoreValidator
     org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:50)
     org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:407)
     org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:179)
     org.apache.jasper.compiler.TagLibraryInfoImpl.<init>(TagLibraryInfoImpl.java:181)
     org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:418)
     org.apache.jasper.compiler.Parser.parseDirective(Parser.java:483)
     org.apache.jasper.compiler.Parser.parseElements(Parser.java:1539)
     org.apache.jasper.compiler.Parser.parse(Parser.java:126)
     org.apache.jasper.compiler.ParserController.doParse(ParserController.java:211)
     org.apache.jasper.compiler.ParserController.parse(ParserController.java:100)
     org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:146)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:286)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:267)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:255)
     org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:556)
     org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:296)
     org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
     org.apache.jasper.servlet.JspServlet.service(JspServlet.java:245)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:322)
     com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:130)
     com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:87)
     com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:200)
     com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:117)
     javax.faces.webapp.FacesServlet.service(FacesServlet.java:198)
     com.stufftolet.view.util.SecurityFilter.doFilter(SecurityFilter.java:70)
     de.mindmatters.faces.spring.RequestHandledFilter.doFilter(RequestHandledFilter.java:117)
Appreciate if someone could give some help here, Thanks !
regards,
kmthien

Hi
I am also facing the same problem. But I am using tomcat 5.0.xx and i havnt included extra jsp-api in the lib. But getting the error
JSP Parsing Error:Failed to load or instantiate TagLibraryValidator class: com.sun.faces.taglib.jsf_core.CoreValidator
tried all the options...but yet not got where is the problem.
Please help.

Unable to read TLD "META-INF/jsf_core.tld" from JAR file "file:

Hallo everybody :-)<br /><br />i've installed Workflow-Server + ARES + FormManager. When i call localhost:8080/adminui i can log in and the browser loads the next site --> it fails and says:<br /><br />org.apache.jasper.JasperException: Unable to read TLD "META-INF/jsf_core.tld" from JAR file "file:/C:/Adobe/LiveCycle/jboss/server/all/tmp/deploy/tmp56414LiveCycle.ear-contents/admi nui.war/WEB-INF/lib/jsf-impl.jar": org.apache.jasper.JasperException: Failed to load or instantiate TagExtraInfo class: com.sun.faces.taglib.FacesTagExtraInfo<br /> org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:5 0)<br /> org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:409)<br /> org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:183)<br /> org.apache.jasper.compiler.TagLibraryInfoImpl.<init>(TagLibraryInfoImpl.java:181)< br /> org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:418)<br /> org.apache.jasper.compiler.Parser.parseDirective(Parser.java:483)<br /> org.apache.jasper.compiler.Parser.parseElements(Parser.java:1539)<br /> org.apache.jasper.compiler.Parser.parse(Parser.java:126)<br /> org.apache.jasper.compiler.ParserController.doParse(ParserController.java:220)<br /> org.apache.jasper.compiler.ParserController.parse(ParserController.java:101)<br /> org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:203)<br /> org.apache.jasper.compiler.Compiler.compile(Compiler.java:470)<br /> org.apache.jasper.compiler.Compiler.compile(Compiler.java:451)<br /> org.apache.jasper.compiler.Compiler.compile(Compiler.java:439)<br /> org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:511)<br /> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:295)<br /> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)<br /> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)<br /> javax.servlet.http.HttpServlet.service(HttpServlet.java:810)<br /> com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:322)<b r /> com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:130)<br /> com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:87)<b r /> com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:200)<br /> com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:117)<br /> javax.faces.webapp.FacesServlet.service(FacesServlet.java:198)<br /> com.adobe.framework.SecurityFilter.doFilter(SecurityFilter.java:177)<br /> com.adobe.idp.um.auth.filter.PortalSSOFilter.doFilter(PortalSSOFilter.java:106)<br /> com.adobe.framework.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter .java:161)<br /><br />Any idea what' wrong?<br /><br />Thanks,<br />Valerio

Hi Howard,
thank you for your post.
I actually new about the problems with the jvm version. Still i wanted to ask, cause there are different reports on this `java problems` and even though the 1.4.2_08 seems to be the best version (by the way this version is not to be downloaded any longer *sig*), there are people getting all installed with other versions. I couldn't find any regularity in the misbehavior of the servers while installing.
I finally achieved and got everything working ... but very slow. Loading the adminui or BAM features takes very long time (over one minute). Have you already had this delay. Any hint?
Thanks again,
Valerio

Unable to find/read file META-INF/ra.xml

When using the oc4j_admin_client to deploy an ear to a oas cluster I get this error, but only sometimes. I cannot find anything on the web that explains what might be causing this to occur. I'm guessing it might be with the configuration of OAS but even so I have no idea where to look. If anyone out there can give some advice it would help. Thanks,
[Summary] There are total 1 instances in the operation.
[Summary] Operation failed on applicationServerName/instanceName
[Summary] Operation on cluster FAILED since 1 instanced failed!
FINE: CoreRemoteMBeanServer.release call release on CoreRemoteMBeanServer: oracle.oc4j.admin.management.mejb.MEjb@5c1ae90c
FINE: CoreRemoteMBeanServer.release Call remove on MBeanServer EJB
FINE: CoreRemoteMBeanServer.release Call close on RMI Context: javax.naming.InitialContext@1629ce8c
SEVERE: J2EEDeploymentManager.deploy Deploy error: Operation failed with error:
Unable to find/read file META-INF/ra.xml in D:\oracle\u01\oas\10.1.3\j2ee\instanceName\connectors\AppName\AppName archive (IO Error: D:\oracle\u01\oas\10.1.3\j2ee\instanceName\connectors\AppName\AppName (The system cannot find the pat
h specified))
oracle.oc4j.admin.deploy.api.J2EEDeploymentException: Operation failed with error:

Hi forum-hog,
I think this is due to a known product defect. The patch is available and can be downloaded and installed.
Please try the following:
1) Download and apply patch 9073284
2) Perform the deployment again
Hope this helps.
Thanks,
Cris

HELP ! unable to read TLD

Hi
I've tried to run a jsp page that uses the following taglib attribute:
<%@ taglib prefix="c" uri="http://java.sun.com/jstl/core" %>
but it comes up with the error message :
Unable to read TLD "META-INF/c-1_0.tld" from JAR file "file:/C:/jakarta/jakarta-tomcat-5.0.19/webapps/ROOT/WEB-INF/lib/standard.jar": java.lang.IllegalStateException: zip file closed
I've unzipped the standard.jar file to make sure that the c-1_0.tld file is there and it is actually there, I've also downloaded the latest version of the taglib but both actions have not solved my problem.
The same error message comes up when i use the taglib
<%@ taglib prefix="sql" uri="http://java.sun.com/jstl/sql" %>
it says
Unable to read TLD "META-INF/sql-1_0.tld" from JAR file "file:/C:/jakarta/jakarta-tomcat-5.0.19/webapps/ROOT/WEB-INF/lib/standard.jar": java.lang.IllegalStateException: zip file closed.
This is really slowing things down as I cant get to use any of the standard taglib
please I need help
abiose

the problem has been solved after i deleted the
web.xml in the web-inf folder??
could somebody please tell me why??
could it be that there were some wrong settings in
the web.xml?Possibly. If your web.xml had any taglib definitions in it related to JSTL, then yes, it was set upt incorrectly.
Another possibility was that there was something wrong someplace else that had been fixed but the context not restarted and so the fix wasn't seen. Then the removal of the web.xml forced the context to be reloaded which showed the firx from earlier.
As a side note, you should put back a web.xml, even if it is an empty <web-app ...></web-app>.

SPRING App through JBOSS - error:Unable to read TLD

Hello,
First post for me, not 100% certain I am in the right forum, but here I go.
I am using Eclipse 3.1, JRE j2sdk1.4.2, spring-framework-1.2, and JBOSS 3.2.7 to follow this tutorial
http://www.springframework.org/docs/MVC-step-by-step/Spring-MVC-step-by-step-Part-2.html
on building a simple Spring MVC application.
I am using jstl.jar,standard.jar (among others) from the spring-framework-1.2 release. I noticed JBOSS starting to go nuts after adding these 2 jars specifically.
My project .war is deployed to JBOSS containg a WEB-INF/lib storing the .jars (standard.jar, jstl.jar ...) I do not have these .jars configured in JBOSS' classpath.
When I run my app and hit my my servlet followed by jsp page, JBOSS reports a runtime exception.
jsp...
<%@ include file="/WEB-INF/jsp/include.jsp"%>
<html>
<head>
<title>Hello :: Spring Application</title>
</head>
<body>
<h1>Hello - Spring Application</h1>
<p>Greetings, it is now <c:out value="${now}" /></p>
</body>
</html>
exception...
: Servlet.service() for servlet jsp threw exception
org.apache.jasper.JasperException: /index.jsp(1,1) Unable to read TLD "META-INF/c.tld" from JAR file "file:/C:/java/jboss-3.2.7/server/default/tmp/deploy/tmp3725spring_app.war/WEB-INF/lib/standard.jar": org.apache.jasper.JasperException: Failed to load or instantiate TagLibraryValidator class: org.apache.taglibs.standard.tlv.JstlCoreTLV
at org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:39)
I confirmed that this standard.jar is deployed/accessible, and the tld is present.
any ideas?
Thanks,
Chris

Hi
I am also facing the same problem. But I am using tomcat 5.0.xx and i havnt included extra jsp-api in the lib. But getting the error
JSP Parsing Error:Failed to load or instantiate TagLibraryValidator class: com.sun.faces.taglib.jsf_core.CoreValidator
tried all the options...but yet not got where is the problem.
Please help.

Unable to read facec-config.xml in META-INF folder of webui-jsf.jar

Hi
I was getting following error when I placed webui-jsf.jar file in websphere 6.0 server
/WEB-INF/lib/jsf-extensions-dynamic-faces-0.1.jar!/META-INF/faces-config.xml
Digester E org.apache.commons.digester.Digester error Parse Error at line 24 column 14: Document is invalid: no grammar found.
org.xml.sax.SAXParseException: Document is invalid: no grammar found.
Do I need to add any other parser to read this file ?
Thanks
Himaja

Your classpath is polluted with different JSF implementations/versions. Clean it up.

Visual Web JSF web app unable to render. The theme tries to access META-INF

Hi,
BACKGROUND: I have created a Netbeans 6 Visual Web Project using the default Visual Web JSF Theme. My web application can be viewed properly and correctly when i deploy it on tomcat 6.
ARCHITECTURE: Our server configuration requires IIS to be our web server and tomcat to be our app server. Both are running on different machines. I have successfully linked up IIS 6 and tomcat 6 using the JK isapi_redirector.
PROBLEM: However, when i connect to my app via IIS, my starting page opens but the input box components on that page are not displayed and i get several javascript errors that read - 'dojo is undefined' and 'webui is undefined'.
PROBLEM DETAILS: I found that the page being served had a lot of files being requested from a META-INF folder. I have attached a snippet here.
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xmlns:wairole="http://www.w3.org/2005/01/wai-rdf/GUIRoleTaxonomy#" xmlns:waistate="http://www.w3.org/2005/07/aaa">
<head>
<title></title><link rel="stylesheet" type="text/css" href="/BMC/theme/com/sun/webui/jsf/suntheme4_1_1/css/css_master-all.css" /><link rel="stylesheet" type="text/css" href="/BMC/theme/com/sun/webui/jsf/suntheme4_1_1/css/ie.css" /><script type="text/javascript">var djConfig={"parseOnLoad":false,"isDebug":false}</script><script type="text/javascript" src="/BMC/theme/META-INF/json2_0/json.js"></script><script type="text/javascript" src="/BMC/theme/META-INF/prototype1_5/prototype.js"></script><script type="text/javascript" src="/BMC/theme/META-INF/com_sun_faces_ajax.js"></script><script type="text/javascript" src="/BMC/theme/META-INF/dojo1_0_1/dojo/dojo.js"></script><script type="text/javascript" src="/BMC/theme/META-INF/dojo1_0_1/dijit/dijit.js"></script><script type="text/javascript">dojo.registerModulePath("webui.suntheme", "/BMC/theme/com/sun/webui/jsf/suntheme4_1_1/javascript");</script><script type="text/javascript" src="/BMC/theme/com/sun/webui/jsf/suntheme4_1_1/javascript/webui-jsfx.js"></script><script type="text/javascript">webui.suntheme.bootstrap.init({"debug":false,"theme":{"locale":"en-US","prefix":"/BMC/theme","modulePath":"/com/sun/webui/jsf/suntheme4_1_1/javascript/theme","bundle":"suntheme","module":"webui.suntheme.theme"}});</script><link id="link1" rel="stylesheet" type="text/css" href="/BMC/resources/stylesheet.css" />I think the JK isapi_connector in IIS is preventing access to the META-INF path and the isapi_director log file says - "*+[emerg] HttpFilterProc::jk_isapi_plugin.c (1282): [BMC/theme/META-INF/json2_0/json.js] points to the web-inf or meta-inf directory. Somebody tries to hack into the site!!!+*". The same message is repeated for several more javascript files that are being served from under the META-INF path.
Any help or advice in this matter will be greatly appreciated.
Thanks!!!

I managed to find a workaround. Thought i should share it with those who are faced with a similar issue.
I found that a bug report had been placed in the past with Apache Dev. However, they had said that they would not modify their logic because the servlet container spec requires it (even though isapi_redirector is only a connector and not a container). They said that there is no way for the isapi_redirector to differentiate between /foo/WEB-INF when foo is a context and when foo is just a sub-directory of the ROOT web application. So, the general consensus was to err on the side of safety and risk blocking a few requests that are valid.
However, this causes a serious issue for those using NetBeans JSF Visual Web Projects. Hence, I created my own flavour of isapi_redirector by modifying the code such that this check is not performed and leaving the onus of checking on Tomcat.
For those who are interested, the simplest way to go about this would be to force the function uri_is_web_inf (in jk_isapi_plugin.c ) to always return FALSE.

Error while reading 'META-INF/weblogic-cmp-rdbms-jar.xml

Hi,
I am getting an error running appc. I am upgrading from wl 7 to wl 8.1. ejbc works
fine on wl 7. Anyone seen this before?
[J2EE:160121]Errors encountered while compiling module 'e:\dev\xstatic\tmp\xstatic_Intermediate.jar':
[EJB:011017]Error while reading 'META-INF/weblogic-cmp-rdbms-jar.xml'. The error
was:
java.lang.NullPointerException
at weblogic.ejb20.cmp.rdbms.finders.ExprWHERE.init_method()V(ExprWHERE.java:47)
at weblogic.ejb20.cmp.rdbms.finders.BaseExpr.init(Lweblogic.ejb20.cmp.rdbms.finders.QueryContext;Lweblogic.ejb20.cmp.rdbms.finders.QueryNode;)V(BaseExpr.java:230)
at weblogic.ejb20.cmp.rdbms.finders.ExprROOT.init_method()V(ExprROOT.java:89)
at weblogic.ejb20.cmp.rdbms.finders.BaseExpr.init(Lweblogic.ejb20.cmp.rdbms.finders.QueryContext;Lweblogic.ejb20.cmp.rdbms.finders.QueryNode;)V(BaseExpr.java:230)
at weblogic.ejb20.cmp.rdbms.finders.QueryContext.generateQuery()V(QueryContext.java:91)
at weblogic.ejb20.cmp.rdbms.finders.Finder.computeSQLQuery(Lweblogic.ejb20.cmp.rdbms.RDBMSBean;)V(Finder.java:1002)
at weblogic.ejb20.cmp.rdbms.RDBMSBean.generateFinderSQLStatements(Ljava.util.Iterator;)V(RDBMSBean.java:2692)
at weblogic.ejb20.cmp.rdbms.Deployer.readTypeSpecificData(Ljava.io.InputStream;Ljava.lang.String;)V(Deployer.java:479)
at weblogic.ejb20.persistence.PersistenceType.setTypeSpecificFile(Lweblogic.ejb20.interfaces.EntityBeanInfo;Lweblogic.ejb20.persistence.spi.CMPDeployer;)V(PersistenceType.java:483)
at weblogic.ejb20.persistence.PersistenceType.setupDeployer(Lweblogic.ejb20.interfaces.EntityBeanInfo;Ljava.io.File;Lweblogic.utils.Getopt2;Lweblogic.utils.jars.VirtualJarFile;)Lweblogic.ejb20.persistence.spi.CMPDeployer;(PersistenceType.java:414)
at weblogic.ejb20.deployer.CMPInfoImpl.setup(Ljava.io.File;Lweblogic.utils.Getopt2;Lweblogic.utils.jars.VirtualJarFile;)V(CMPInfoImpl.java:113)
at weblogic.ejb20.ejbc.EJB20CMPCompiler.generatePersistenceSources(Lweblogic.ejb20.interfaces.EntityBeanInfo;Lweblogic.utils.jars.VirtualJarFile;)Ljava.util.List;(EJB20CMPCompiler.java:64)
at weblogic.ejb20.ejbc.EJBCompiler.doCompile(Ljava.util.Collection;Lweblogic.utils.jars.VirtualJarFile;)V(EJBCompiler.java:245)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(Lweblogic.utils.classloaders.GenericClassLoader;Lweblogic.management.configuration.EJBComponentMBean;Lweblogic.management.descriptors.toplevel.EJBDescriptorMBean;Lweblogic.utils.jars.VirtualJarFile;Lweblogic.j2ee.valid
ation.ModuleValidationInfo;Lweblogic.ejb20.ejbc.VersionHelper;Ljava.util.Collection;)V(EJBCompiler.java:468)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(Lweblogic.utils.classloaders.GenericClassLoader;Lweblogic.utils.jars.VirtualJarFile;Lweblogic.j2ee.validation.ModuleValidationInfo;)V(EJBCompiler.java:387)
at weblogic.appc.compileEJB(Lweblogic.utils.classloaders.GenericClassLoader;Lweblogic.utils.jars.VirtualJarFile;Ljava.io.File;Lweblogic.j2ee.validation.ModuleValidationInfo;)V(appc.java:735)
at weblogic.appc.compileEJB()V(appc.java:709)
at weblogic.appc.compileInput()V(appc.java:446)
at weblogic.appc.runBody()V(appc.java:167)
at weblogic.utils.compiler.Tool.run([Ljava.lang.String;)V(Tool.java:146)
at weblogic.utils.compiler.Tool.run()V(Tool.java:103)
at weblogic.appc.main([Ljava.lang.String;)V(appc.java:961)

It is a bug for the EJB container to respond with an NPE.
(It's been fixed in v9 Beta, and it might be fixed in an 8.1 service pack but I can't recall off the top of my head). At any rate, I'm pretty sure that an EJB QL query with an empty WHERE clause will cause this. I would look for a query that ends in ' WHERE'.
-thorick

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

I have succesully deployed an external generated WAR file using the Developer Studio 'Deploy View'. However, I get an exception at runtime:
com.sap.engine.services.servlets_jsp.jspparser_api.exception.JspParseException: Error in parsing the taglib tag in the JSP page. Cannot resolve URI: [http://www.some.url/some/location].
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.
Could this be a bug in the J2EE Preview? Any workarounds here?
Enrique

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

Reading META-INF contents from an annotation processor

Hello,
I'm trying to read the contents of META-INF with my annotation processor, something akin to:
@Override
public boolean process(
Set<? extends TypeElement> annotations, RoundEnvironment roundEnv)
try {
FileObject resource = processingEnv.getFiler().getResource(
StandardLocation.SOURCE_PATH, "META-INF.services", "javax.annotation.processing.Processor");
String filecontents = new Scanner(resource.openInputStream()).useDelimiter("\\A").next();
processingEnv.getMessager().printMessage(Kind.NOTE, filecontents);
} catch (IOException ex) {
processingEnv.getMessager().printMessage(Kind.ERROR, ex.toString());
return true;
(But against something that is relevant for my processor.) But when I do that I get:
error: javax.annotation.processing.FilerException: Illegal name META-INF.services
Bug, or shouldn't annotation processors be reading the contents of META-INF anyhow?
Thanks,
Thor Michael

META-INF/services

How to get and read a file from META-INF directory

how to get and read a file from META-INF directory in a EJB project

Use this.getClass().getResourceAsStream("/META-INF/filename");This should work. Probably, you would need to set the Manifest Class-Path attribute.

Failed to load META-INF/application.xml when upgrading to wls9.2

We are migrating our weblogic server from 8.1 to 9.2. Tried to use DDConverter to convert the EJB deployment descriptor, but when I ran weblogic.appc, I got the following error :
<i><Error> <J2EE> <BEA-160197> <Unable to load descriptor D:\workspace\webshopEJB\wl9.2/META-INF/application.xml of module webshopLogic. The error is weblogic.descriptor.DescriptorException: Unmarshaller failed</i>
and
<i>Caused by: com.bea.xml.XmlException: failed to load java type corresponding to e=application@http://java.sun.com/xml/ns/j2ee</i>
Here is my application.xml
<b><?xml version="1.0" encoding="UTF-8"?>
<application xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.4">
<description>webshop EJB module</description>
<display-name>webshop Logic EJB</display-name>
<module>
<ejb>webshopLogic</ejb>
</module>
</application></b>
I checked for classpath, and still no clue about what's going wrong. Thanks in advance for any help.

I believe this likely is a classpath problem. I'd start by using the setWLSEnv.cmd or .sh script in the kit. That should set the classpath correctly.
Also, FWIW it wasn't required to run DDConverter. You could have used your 8.1 descriptors unchanged in 9.x as well.
-- Rob
WLS Blog http://dev2dev.bea.com/blog/rwoollen/

Problem deploying connector: META-INF/ejb-jar.xml not found in jar file

          Has anyone seen this problem:
          I built Sun's Blackbox implementation and packaged
          it identical to the BlackBoxNoTx.rar included with
          Weblogic's 'jconnector' sample (even using the same
          ra.xml and weblogic-ra.xml). When I try to deploy
          it, the server reports:
          java.io.FileNotFoundException:
          META-INF/ejb-jar.xml not found in jar file
          I have no idea why the server thinks my connector
          is an EJB. If I deploy the BlackBoxNoTx.rar included
          with the sample, everything works without a hitch.
          The only variable that I'm changing in my BlackBoxNoTx.rar
          is that I build the Blackbox classes myself--otherwise,
          the RAR packagings are identical. Any assistance is
          greatly appreciated since I'm banging my head against
          a wall...
          Thanks,
          -jason


          I was finally able to resolve this one. On the odd chance that someone else encounters
          the same problem, here's what went wrong:
          My RAR file had two directories: 'META-INF' and 'meta-inf'. The first was created
          by the jar tool and contained the manifest.mf file. The second I created manually
          and it contained my ra.xml and weblogic-ra.xml. When I examined the RAR using
          any tools or I extracted the contents, it looked like it only contained one directory:
          META-INF (because NT is case-insensitive).
          "Jason L" <[email protected]> wrote:
          >
          >Has anyone seen this problem:
          >
          >I built Sun's Blackbox implementation and packaged
          >it identical to the BlackBoxNoTx.rar included with
          >Weblogic's 'jconnector' sample (even using the same
          >ra.xml and weblogic-ra.xml). When I try to deploy
          >it, the server reports:
          >
          >java.io.FileNotFoundException:
          >META-INF/ejb-jar.xml not found in jar file
          >
          >I have no idea why the server thinks my connector
          >is an EJB. If I deploy the BlackBoxNoTx.rar included
          >with the sample, everything works without a hitch.
          >The only variable that I'm changing in my BlackBoxNoTx.rar
          >is that I build the Blackbox classes myself--otherwise,
          >the RAR packagings are identical. Any assistance is
          >greatly appreciated since I'm banging my head against
          >a wall...
          >
          >Thanks,
          >
          >-jason

I have a mac osx 10.411G4 powre pc and recently I down loaded excel for mac 2004 the problem that iam having is that the two other programs i downloaded one program it says unable to read the dictionary of the application of the extension because it is no

I have a mac osx 10.411 power pc and recently i downloaded excel for mac 2004 so that i could download some program that only would work if i have excel for mac but what happen was it went to script and said that unable to read the dictionary of the application of the extension because it is not scriptable and the second pop up said the document autorun,inf could not open script editor can not open files in script editor app can any one help me how do i get these program working thank you norro460

good afternoon Limnos i think i didnt give the right info I didnt download well in a way i did i bought a copy of microsoft excel for mac 2004 i loaded on to my mac then i went and down loaded some software that said i needed to have excel you see my mac is osx 10.4,11 power pc G4 and that is were i had the problem now the excell loaded allright but the the other programs did not the pop ups say it is not scriptable or can not read dictionary if you can help m,e iam not great with computers but i along

Unable to read TLD "META-INF/c-1_0.tld"

Similar Messages

Maybe you are looking for