Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Oracle Community by Justin_Michael_Raj, 1 year ago
, please ensure the META-INF/application.xml exists. EJB-JARs should have a META-INF/ejb-jar.xml or corresponding annotations exist. If this is an exploded WAR, the name of directory must be end with ".war". RARs require a META-INF/ra.xml. A JMS deployment
via Oracle Community by RobertMetcalf, 1 year ago
/application.xml exists. EJB-JARs should have a META-INF/ejb-jar.xml or corresponding annotations exist. If this is an exploded WAR, the name of directory must be end with ".war". RARs require a META-INF/ra.xml. A JMS deployment should be an XML file whose name
via Oracle Community by 663131, 2 years ago
/application.xml exists. EJB-JARs should have a META-INF/ejb-jar.xml or corresponding annotations exist. If this is an exploded WAR, the name of directory must be end with ".war". RARs require a META-INF/ra.xml. A JMS deployment should be an XML file whose
via Oracle Community by 673954, 2 years ago
a META-INF/ejb-jar.xml. WAR files require a WEB-INF/web.xml, and RARs require a META-INF/ra.xml. A JMS deployment should be an XML file whose name ends with "-jms.xml". A JDBC deployment s hould be an XML file whose name ends with "-jdbc.xml". For other application types, please consult the WebLogic Server docum entation.
via theserverside.com by Unknown author, 2 years ago
META-INF/ejb-jar.xml. WAR files require a WEB-INF/web.xml, and RARs require a META-INF/ra.xml. A JMS deployment should be an XML file whose name ends with "-jms.xml". A JDBC deployment s hould be an XML file whose name ends with "-jdbc.xml". For other application types, please consult the WebLogic Server docum entation.
via Oracle Community by dwhpc, 2 years ago
META-INF/application.xml exists. EJB-JARs should have a META-INF/ejb-jar.xml or corresponding annotations exist. If this is an exploded WAR, the name of directory must be end with ".war". RARs require a META-INF/ra.xml. A JMS deployment should be an XML
weblogic.management.DeploymentException: [J2EE:160177]
The application
at "C:\Oracle\orasoa11g\wls\Middleware\user_projects\domains\soa_domain\servers\soa_server1\stage\sca_mediator1_rev1\sca_mediator1_rev1.0.jar" was not recognized as a valid application type.
If this is an EAR file, please ensure the META-INF/application.xml exists.
EJB-JARs should have a META-INF/ejb-jar.xml or corresponding annotations exist.
If this is an exploded WAR, the name of directory must be end with ".war". RARs require a META-INF/ra.xml.
A JMS deployment should be an XML file whose name ends with "-jms.xml".
A JDBC deployment should be an XML file whose name ends with "-jdbc.xml".
For other application types, please consult the WebLogic Server documentation.	at weblogic.application.internal.DeploymentManagerImpl.createDeployment(DeploymentManagerImpl.java:106)	at weblogic.deploy.internal.targetserver.BasicDeployment.createDeployment(BasicDeployment.java:149)	at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:202)	at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)	at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)	at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:749)	at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)	at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)	at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:160)	at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)	at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)	at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:47)	at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)	at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)	at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)