EAR META-INF generation failed:null

Hi there,
I am using local NWDS to create a DC project for Composite Application Service, but the system gives me this error "EAR META-INF generation failed:null". I tried to delete the metadata folder, it does not work. When I create the same project on server side, no problem at all.
Thanks,
Frank

Most probably the Eclipse workspace has some problems. In order to check this, do the following: open Help|About, and check whether the three icons for SAP, Borland end Eclipse.org are visible. If not, this is a certain indicator of a corrupted Eclipse workspace.
So, if the workspace is broken, here are the two options:
1. Reinstall the IDE using the setup program (i.e. not just extracting the eclipse directory). Might not work.
2. Reset the workspace (by deleting the directory C:\Documents and Settings\username\Documents\SAP\workspace\.metadata (in case the default workspace location is used)) and recreate your projects again (warning: you will also lose various settings like the nameserver, J2EE server, Java editor preferences, etc). This solution is actually quite faster than 1, and works always.
Hope this helps.

Similar Messages

Deploying EJB JAR and Application EAR, META-INF directory name

To all:
I had a problem the last couple of days with deploying an EJB and application.
I'm new to WebLogic, maybe this is common knowledge, but I researched it and
didn't find any reference to what I discovered.
I'm using WebLogic Server 7 Service Pack 2 (7.02), on Windows 2000.
My problem was that the application that I was trying to deploy would not deploy
successfully, because a dependent class was not found for the EJB. I tried everything,
but the only thing I could get to work was placing the dependent jar files in
the classpath of the WebLogic server, within the start script. I correctly had
the Class-Path manifest line correct, but the dependent classes were not being
found.
Through trial and error I discovered that the META-INF directory within the JAR
and EAR archives HAS TO BE ALL UPPERCASE for the app server to successfully find
the manifest.mf file and the application.xml file.
As soon as I changed the directory name in both the EJB JAR file and the application
EAR file, the EJB deployed successfully, all dependent classes were then found.
I'm posting this here to help anybody that might have the same problem. There
is not any documentation that I could find that had this directory name requirement
explicitly stated.
Regards,
JD

What does the manual for the OC4J application server have to say about it all?

Cisco ISE 1.1.1.268 Giving error (Report Generation failed. Cause: Null)

I have this issue and I would be very thankful if someone has the answer for this. When I am trying to access Operation > Report > Catalog > Posture > Posture Detail Assessment & clicking on any posture session detail icon. I am getting following attached errors.
1. Report Generation failed. Cause: Null
2. Cannot execute the statement.
Does anyone knows how to get rid of this error & to get access of posture detail.
Thanks

The error message means that Active Directory server Reject the authentication attempt
as for some reasons the user account got locked.I guess, You should ask your AD Team to check in the AD
Event Logs why did the user account got locked.
Under Even Viewers, You can find it out
Regards
Minakshi (Do rate the helpful posts)

No META-INF/application.xml was found in the EAR

I create a EAR using:
jar -cvf e:\workspace\otnapp\otnapp.ear
Then, I depoy this EAR through:
e:\jdk160_18\bin>java weblogic.Deployer -adminurl t3:\\localhost:7001 -user weblogic -passwork welcome1 -deploy -upload e:\workspace\otnapp\otnapp.ear
But, I get errors as follow:
java.io.IOException: No META-INF/application.xml was found in the EAR otnapp.ear
How to change the jar in the command line?

otnapp is an adf web application. META-INF is not in the E:\soaworkspace\otnapp.
It is in the :
E:\SOAworkspace\otnapp\.adf\META-INF
E:\SOAworkspace\otnapp\Model\classes\META-INF
E:\SOAworkspace\otnapp\src\META-INF
None of them contains application.xml.
I run jar in E:\soaworkspace\otnapp. But I get error : 'jar' is not recognized as an internal or external command, operable program or batch file.
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Administrator>d:
D:\>e:
E:\>cd E:\soaworkspace\otnapp
E:\SOAworkspace\otnapp>jar -cvf otnapp.ear
'jar' is not recognized as an internal or external command, operable program or batch file.
E:\SOAworkspace\otnapp>jar -cvf otnapp.ear */ .
'jar' is not recognized as an internal or external command, operable program or batch file.
E:\SOAworkspace\otnapp>set java_home
JAVA_HOME=E:\OracleBI_win2008_32_20101206\jdk160_18
path=
CD:\apache-maven-2.0.11\bin;C:\app\Administrator\product\11.2.0\dbhome_1\bin;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Program Files\Common Files\Thunder Network\KanKan\Codecs;C:\apps\FME\;C:\Program Files\Subversion\bin;C:\Program Files\TortoiseSVN\bin;D:\win2008EclipseWorkspace;E:\OracleBI_win2008_32_20101206\Oracle_BI1\bin;E:\OracleBI_win2008_32_20101206\Oracle_BI1\opmn\bin;E:\OracleBI_win2008_32_20101206\Oracle_BI1\opmn\lib;E:\OracleBI_win2008_32_20101206\Oracle_BI1\perl\bin;%JAVA_HOME%\bin;CATALINA_HOME\bin;C:\Users\Administrator>E:\SOAworkspace\otnapp>

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 :
<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
and
Caused by: com.bea.xml.XmlException: failed to load java type corresponding to e=application@http://java.sun.com/xml/ns/j2ee
Here is my application.xml
<?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>
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/

How to use ClassPath defined in META-INF/MANIFEST.MF in an EAR

Hi,
We have an EAR Shared Library (Name = AA) deployed in Weblogic. EAR contents are like ->
APP-INF/lib/directoryA/<<50 JAR Files>>
META-INF/MANIFEST.MF --->> Has Class Path to above JAR files, Spec Version, Impl Version etc
META-INF/application.xml
META-INF/weblogic.application.xml
This EAR is deployed as Shared Library, and our EJB (name = BB) refers to this EAR. Now the problem we are facing is that the JARs are not reachable by EJB BB. If we restructure the Shared Library project so that all the JARS are under APP-INf/lib/ directory, we are able to access the JARS from EJB BB. (This means that we are referring the shared library correctly, using "library-ref" tag correctly.
Is there a way we can specify EJB BB to look for CLASS PATH as present in the MANIFEST.MF file of the Shared Library ??
Thanks,

WebLogic specifies a separate classloader for the APP-INF/lib directory that is why it gets loaded
When you have some.jar file placed in an arbitrary directory, for example, somewhere. You can either
use application.xml, for example,
<application ...>
 <module>
 <ejb>EJB.jar</ejb>
 </module>
 <module>
 <web>
 <web-uri>Web.war</web-uri>
 <context-root>MiddlewareMagic</context-root>
 </web>
 </module>
 <library-directory>somewhere</library-directory>
</application> Or by using the manifest Class-Path entry option which requires adding a META-INF/MANIFEST.MF file with the following contents:
Manifest-Version: 1.0
Class-Path: somewhere/some.jarMore information on class loading and application packaging can be found here: http://middlewaremagic.com/weblogic/?p=6725

EAR generation failed: Error calling Ant to jarSap archive

Hi,
I can't create the EARs in NetWeaver Developer Studio anymore. It is not possible for proxies and for Webservices. I got the error message: EAR generation failed: Error calling Ant to jarSap archive.
What could be the problem?
Thank you!
Julia

Hi,
when I try to build the application archive before I can deploy a webservice, I got the error message: "EAR genearation failed! Reason: Error calling Ant to jarSap archive". When I try to generate the EAR for a proxy I got no error message at all but the EAR is not generated.
Thank you!
Julia

EAR generation failed

Dear all,
We encountered the Ear generation failed error. reason : Error calling Ant to jarSap archive, while i'm trying to generate EAR.
In sdn, somebody solved this problem by removing old workspace and creating a new one.
Could anyone guide me how to remove old workspace and create a new one ?
Thanks in advance.
Regards,
Vijay.

hi,
Refer sap note 855537 ...its about deleting workspace folders.
Regards
Jayapriya

WEB-INF/lib (.war) Vs META-INF/MANIFEST.MF (.ear)

What are the Class loading differences between libraries that are in a web application web-inf/lib and that are in class-path entry of META-INF/manifest.mf of a ear.
I recently developed a web services application with a ejb endpoint.Then
packaged it in a ear file with the classpath entry .The problem occured when I placed the weblogic.jar(and other third party jars) in the ear file which my ejb.jar uses as utility jar's. Jboss starts behaving weird.Some of the classes of jboss are overwritten and class cast exception errors started coming up.
Overnight I changed the application to a servlet end point and placed all my jars in the WEB-INF/lib then everything started working smooth.
Can any body help me , understand what is happening. Why doesn't j2ee have something like META-INF/lib

What did you do to resolve this issue .. I'm having the exact same problem.
What a nightmare.
I found approximately 40 forums on this topic (and
there are probably more), but noone has the definitive
answer!
Here's the problem....
My servlet uses a utility class that resides in some
other jar. That jar is then placed into the
WEB-INF\lib directory of the WAR which in turn goes
into the EAR. This is supposed to be all that is
needed in order for the utility class to be found on
the classpath.
In fact, if you run the war in Tomcat as a standalone
WAR it does in fact find it.... its when in an EAR
deloployed to app server that the problem arises.
I have had no luck with using any combination of
putting the jar ANYWHERE in the EAR or WAR no matter
if I specify the Class-Path: in the manifest(s) or
not.
I thought maybe that I was missing some config in the
application.xml or web.xml but I couldn't find
anything to support that.
Maybe its dependent on the app server? I am using
Orion, but the same problem can be found on J2EE RI
release 1.3
Work arounds:
1. Simply put the utility jar in the lib directory of
the server you're using
2. Add an ejb module to the application.xml naming the
utility jar as the ejb jar. Of course this is NOT an
EJB jar and error messages/warnings will appear
accordingly, but on Orion at least, it will load the
classes needed... hooray!!
Anyone got a definitive answer?

Generation of PublicPartFileList.xml failed: null

Hi Experts
I m facing a problem with my DC project. I want to use the component of my DC in Other DC Project.I created its public part and added them in the Second DCs Used DC node.
After builing the first DC i m getting a warning as below:-
"Generation of PublicPartFileList.xml failed: null"
And so when i build my second DC its getting failed as its not getting the used DC puplic parts.
Can anyone help me why this PublicPart.xml couldnot be created.Is there any file to be added to the build path or any thing else that i m missing.
Regards
DhanyaR Nair

Hi Yashpal
I have done the same thing.But its still giving warning that the PublicPartFileList.xml generation failed.
I m able to add the publicparts to the second DC project.but build failes as previous warning is causing error to my dependent DCs.
Regards
DhanyaR Nair

WARNING: ExternalInterface generation failed: WebServiceName : null

Hello experts,
I have created a WebService using stateless session bean and deployed it on J2EE server. After successfuly testing that webservice on the server, I tried to include it in a CAF project as an external service.
But when I try to build the project after importing this webserice, I get error stating WARNING: ExternalInterface generation failed: <WebServiceName>: null
Please guide me how do I make it workable.
Regards,
Ashutosh

Hi
Anybody has an update on this issue , i am also trying to create a Webservice in NWDS using BAPI
Thanks
Ram

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

Hallo everybody :-) 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: 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 org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:5 0) org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:409) org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:183) 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:220) org.apache.jasper.compiler.ParserController.parse(ParserController.java:101) org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:203) org.apache.jasper.compiler.Compiler.compile(Compiler.java:470) org.apache.jasper.compiler.Compiler.compile(Compiler.java:451) org.apache.jasper.compiler.Compiler.compile(Compiler.java:439) org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:511) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:295) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236) javax.servlet.http.HttpServlet.service(HttpServlet.java:810) 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.adobe.framework.SecurityFilter.doFilter(SecurityFilter.java:177) com.adobe.idp.um.auth.filter.PortalSSOFilter.doFilter(PortalSSOFilter.java:106) com.adobe.framework.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter .java:161) Any idea what' wrong? Thanks, 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

Persistence.xml under classes/META-INF makes other jar references to miss

Hi,
When I am adding persistence.xml to classes/META-INF folder where classes folder got other packages under it, classes in such packages are not getting reference to respective jar files in lib folder. So, deployment of the web project in OAS (Oracle application server) 10g fails mentioning NoClassDef found for classes from library jars referred. If I remove persistence.xml from here, the war file is getting deployed. Deployment fails even when the persistence.xml is available anywhere in classpath (like WEB-INF).
What is the reason & how to correct it?Any alternative approach like manifest or use some settings in OAS?

Hi,
To be accessible to the EJB JAR, WAR, or EAR file, a class or a JAR file must be on the deployment classpath. You can achieve this in one of the following ways:
Put the JAR file in the manifest classpath of the EJB JAR or WAR file. Do this by adding a classpath entry to the META-INF/MANIFEST.MF file in the JAR or WAR file. You may specify one or more directories or JAR files, separating them by spaces. The following example shows how the manifest file classpath entry adds the employee/emp-classes.jar file and the employee/classes directory to the classpath of the JAR file that contains the manifest file:
Class-Path: employee/emp-classes.jar employee/classes
Place the JAR file in the library directory of the EAR filethis will make this JAR file available on the application classpath and accessible by all of the modules deployed within the EAR file. By default, this would be the lib directory of the EAR file, although you may configure it to be any directory in the EAR file using the library-directory element in the application.xml deployment descriptor. The following example shows the application.xml file:
<application ...>
<library-directory>myDir/jars</library-directory>
</application>
Java EE allows for persistence support in a variety of packaging configurations. You can deploy your application to the following module types:
EJB modules: you can package your entities in an EJB JAR. When defining a persistence unit in an EJB JAR, the persistence.xml file is not optionalyou must create and place it in the META-INF directory of the JAR alongside the deployment descriptor, if it exists.
Web modules: you can use WAR file to package your entities. In this case, place the persistence.xml file in the WEB-INF/classes/META-INF directory. Since the WEB-INF/classes directory is automatically on the classpath of the WAR, specify the mapping file relative to that directory.
Persistence archives: a persistence archive is a JAR that contains a persistence.xml file in its META-INF directory and the managed classes for the persistence unit defined by the persistence.xml file. Use a persistence archive if you want to allow multiple components in different Java EE modules to share or access a persistence unit. The following example shows how to package entities in a persistence archive:
emp.ear
emp-persitence.jar
META-INF/persistence.xml
META-INF/orm.xml
examples/model/Employee.class
examples/model/Phone.class
examples/model/Address.class
examples/model/Department.class
examples/model/Project.class
Once you created a persistence archive, you can place it in either the root or the application library directory of the EAR. Alternatively, you can place the persistence archive in the WEB-INF/lib directory of a WAR. This will make the persistence unit accessible only to the classes inside the WAR, but it enables the decoupling of the definition of the persistence unit from the web archive itself.
Regards,
Vinay

EJB CBS Build Error: No folder found for attribute meta-inf

I'm trying to activate my EJB DC that works properly when built and executed/deployed in the portal.
But in CBS it fails to build and we got the following error trace:
This is the error trace:
[pppacker] Packing public part 'client'
[pppacker] ERROR: Failed to pack public part: No folder found for attribute meta-inf
[pppacker] ERROR:       at com.sap.tc.buildplugin.pp.PPPackTask._execute(PPPackTask.java:295)
[pppacker] ERROR:       at com.sap.tc.buildplugin.techdev.ant.util.BPTask.execute(BPTask.java:20)
[pppacker] ERROR:       at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
[pppacker] ERROR:       at org.apache.tools.ant.Task.perform(Task.java:364)
[pppacker] ERROR:       at org.apache.tools.ant.Target.execute(Target.java:341)
[pppacker] ERROR:       at org.apache.tools.ant.Target.performTasks(Target.java:369)
[pppacker] ERROR:       at org.apache.tools.ant.Project.executeTarget(Project.java:1214)
[pppacker] ERROR: Caused by: com.sap.tc.buildplugin.pp.PackException: No folder found for attribute meta-inf
[pppacker] ERROR:       at com.sap.tc.buildplugin.pp.entity.EHEjbClientJar.findSpecialFolderContaining(EHEjbClientJar.java:126)
[pppacker] ERROR:       at com.sap.tc.buildplugin.pp.entity.EHEjbClientJar.determineFileList(EHEjbClientJar.java:64)
[pppacker] ERROR:       at com.sap.tc.buildplugin.pp.PPPacker.packEntity(PPPacker.java:697)
[pppacker] ERROR:       at com.sap.tc.buildplugin.pp.PPPacker.packPublicPartContent(PPPacker.java:585)
[pppacker] ERROR:       at com.sap.tc.buildplugin.pp.PPPacker.packPublicPart(PPPacker.java:532)
[pppacker] ERROR:       at com.sap.tc.buildplugin.pp.PPPacker.pack(PPPacker.java:460)
[pppacker] ERROR:       at com.sap.tc.buildplugin.pp.PPPackTask._execute(PPPackTask.java:293)
[pppacker] ERROR:       ... 29 more
Ant runtime 0.032 seconds
Ant build finished with ERRORS
Failed to pack public part: No folder found for attribute meta-inf
I'm not sure if this means anything:
Preparing data context..
No public part descriptor found for component "ejb20" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "jdbc20" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "jms" (vendor "sap.com"), public part "default", using legacy mode.
No 'default' JDK defined, will use running VM.
Data context preparation finished in 0.017 seconds
How do I resolve this issue?
Thank you in advance.

TRY TO DO ITSELF.

EAR META-INF generation failed:null

Similar Messages

Maybe you are looking for