on 02-15-2007 4:39 AM
<b>Hi
I have deployed an EJB as a web service, now am trying to create a client using the web service client wizard in NWDS to test the web service. I pass the wsdl url to the wizard for the service definition, move the slider for Test client and change the web service runtime to SAP Netweaver and say Next. Then the wizard asks for the Output Folder and i use the default folder and say Next. Now at this point an error comes which says,</b>
Publishing failed
Error during deployment:
com.sap.ide.eclipse.sdm.deploy.DeploymentException: DeploymentException.
Reason: An error occurred while deploying the deployment item 'sap.com_SummitOrder_140207ClientEAR'.; nested exception is:
java.rmi.RemoteException: class com.sap.engine.services.dc.gd.DeliveryException: An error occurred during deployment of sdu id: sap.com_SummitOrder_140207ClientEAR
sdu file path: C:\SAP\DevStudio\eclipse\workspace\SummitOrder_140207ClientEAR\SummitOrder_140207ClientEAR.ear
version status: NEW
deployment status: Admitted
description:
1. Error:
Error occurred while deploying ear file C:\SAP\DevStudio\eclipse\workspace\SummitOrder_140207ClientEAR\SummitOrder_140207ClientEAR.ear.
Reason: Exception while validating application sap.com/SummitOrder_140207ClientEAR.
No one of the [app_libraries_container, connector] containers, which processed it, returned deployed component names.
The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
Possible reasons :
1.An AS Java service, which is providing a container, is stopped or not deployed.
2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.
. Cannot deploy it.; nested exception is:
java.rmi.RemoteException: class com.sap.engine.services.deploy.server.utils.DSRemoteException: Error occurred while deploying ear file C:\SAP\DevStudio\eclipse\workspace\SummitOrder_140207ClientEAR\SummitOrder_140207ClientEAR.ear.
Reason: Exception while validating application sap.com/SummitOrder_140207ClientEAR.
No one of the [app_libraries_container, connector] containers, which processed it, returned deployed component names.
The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
Possible reasons :
1.An AS Java service, which is providing a container, is stopped or not deployed.
2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.
at com.sap.ide.eclipse.sdm.threading.DCDeployThread.run(DCDeployThread.java:145)
-
Nested exception -
com.sap.engine.services.dc.api.deploy.DeployException: DeploymentException.
Reason: An error occurred while deploying the deployment item 'sap.com_SummitOrder_140207ClientEAR'.; nested exception is:
java.rmi.RemoteException: class com.sap.engine.services.dc.gd.DeliveryException: An error occurred during deployment of sdu id: sap.com_SummitOrder_140207ClientEAR
sdu file path: C:\SAP\DevStudio\eclipse\workspace\SummitOrder_140207ClientEAR\SummitOrder_140207ClientEAR.ear
version status: NEW
deployment status: Admitted
description:
1. Error:
Error occurred while deploying ear file C:\SAP\DevStudio\eclipse\workspace\SummitOrder_140207ClientEAR\SummitOrder_140207ClientEAR.ear.
Reason: Exception while validating application sap.com/SummitOrder_140207ClientEAR.
No one of the [app_libraries_container, connector] containers, which processed it, returned deployed component names.
The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
Possible reasons :
1.An AS Java service, which is providing a container, is stopped or not deployed.
2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.
. Cannot deploy it.; nested exception is:
java.rmi.RemoteException: class com.sap.engine.services.deploy.server.utils.DSRemoteException: Error occurred while deploying ear file C:\SAP\DevStudio\eclipse\workspace\SummitOrder_140207ClientEAR\SummitOrder_140207ClientEAR.ear.
Reason: Exception while validating application sap.com/SummitOrder_140207ClientEAR.
No one of the [app_libraries_container, connector] containers, which processed it, returned deployed component names.
The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
Possible reasons :
1.An AS Java service, which is providing a container, is stopped or not deployed.
2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:734)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:220)
at com.sap.ide.eclipse.deployer.dc.deploy.DeployProcessor70.deploy(DeployProcessor70.java:111)
at com.sap.ide.eclipse.sdm.threading.DCDeployThread.run(DCDeployThread.java:119)
Caused by: com.sap.engine.services.dc.cm.deploy.DeploymentException: An error occurred while deploying the deployment item 'sap.com_SummitOrder_140207ClientEAR'.; nested exception is:
java.rmi.RemoteException: class com.sap.engine.services.dc.gd.DeliveryException: An error occurred during deployment of sdu id: sap.com_SummitOrder_140207ClientEAR
sdu file path: C:\SAP\DevStudio\eclipse\workspace\SummitOrder_140207ClientEAR\SummitOrder_140207ClientEAR.ear
version status: NEW
deployment status: Admitted
description:
1. Error:
Error occurred while deploying ear file C:\SAP\DevStudio\eclipse\workspace\SummitOrder_140207ClientEAR\SummitOrder_140207ClientEAR.ear.
Reason: Exception while validating application sap.com/SummitOrder_140207ClientEAR.
No one of the [app_libraries_container, connector] containers, which processed it, returned deployed component names.
The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
Possible reasons :
1.An AS Java service, which is providing a container, is stopped or not deployed.
2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.
. Cannot deploy it.; nested exception is:
java.rmi.RemoteException: class com.sap.engine.services.deploy.server.utils.DSRemoteException: Error occurred while deploying ear file C:\SAP\DevStudio\eclipse\workspace\SummitOrder_140207ClientEAR\SummitOrder_140207ClientEAR.ear.
Reason: Exception while validating application sap.com/SummitOrder_140207ClientEAR.
No one of the [app_libraries_container, connector] containers, which processed it, returned deployed component names.
The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
Possible reasons :
1.An AS Java service, which is providing a container, is stopped or not deployed.
2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.
at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:186)
at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:47)
at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:177)
at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:76)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:624)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:483)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:206)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:153)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:807)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:253)
at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:109)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:841)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:125)
at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:59)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:168)
Caused by: java.rmi.RemoteException: class com.sap.engine.services.dc.gd.DeliveryException: An error occurred during deployment of sdu id: sap.com_SummitOrder_140207ClientEAR
sdu file path: C:\SAP\DevStudio\eclipse\workspace\SummitOrder_140207ClientEAR\SummitOrder_140207ClientEAR.ear
version status: NEW
deployment status: Admitted
description:
1. Error:
Error occurred while deploying ear file C:\SAP\DevStudio\eclipse\workspace\SummitOrder_140207ClientEAR\SummitOrder_140207ClientEAR.ear.
Reason: Exception while validating application sap.com/SummitOrder_140207ClientEAR.
No one of the [app_libraries_container, connector] containers, which processed it, returned deployed component names.
The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
Possible reasons :
1.An AS Java service, which is providing a container, is stopped or not deployed.
2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.
. Cannot deploy it.; nested exception is:
java.rmi.RemoteException: class com.sap.engine.services.deploy.server.utils.DSRemoteException: Error occurred while deploying ear file C:\SAP\DevStudio\eclipse\workspace\SummitOrder_140207ClientEAR\SummitOrder_140207ClientEAR.ear.
Reason: Exception while validating application sap.com/SummitOrder_140207ClientEAR.
No one of the [app_libraries_container, connector] containers, which processed it, returned deployed component names.
The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
Possible reasons :
1.An AS Java service, which is providing a container, is stopped or not deployed.
2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.
at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.performDeployment(ApplicationDeployer.java:162)
at com.sap.engine.services.dc.gd.impl.GenericDeliveryImpl.deploy(GenericDeliveryImpl.java:54)
at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:157)
... 16 more
Caused by: java.rmi.RemoteException: class com.sap.engine.services.deploy.server.utils.DSRemoteException: Error occurred while deploying ear file C:\SAP\DevStudio\eclipse\workspace\SummitOrder_140207ClientEAR\SummitOrder_140207ClientEAR.ear.
Reason: Exception while validating application sap.com/SummitOrder_140207ClientEAR.
No one of the [app_libraries_container, connector] containers, which processed it, returned deployed component names.
The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
Possible reasons :
1.An AS Java service, which is providing a container, is stopped or not deployed.
2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:302)
at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.performDeployment(ApplicationDeployer.java:150)
... 18 more
<b>Now what can be the reason for this failure, is there any configuration issues with the server which i have to take care of.
Also is there any other way of testing a web service in NWDS. I tried using soap sonar as was specified in one article on SDN, but either you have to but that product or use a trial version, which expires after some days.
Please help me on this.
Thanks & Regards
Bhupesh...</b>
I tried with the project <i>type</i> as 'SAP Application Client Project', then this error comes,
Publishing failed
Error during deployment:
com.sap.ide.eclipse.sdm.deploy.DeploymentException: DeploymentException.
Reason: An error occurred while deploying the deployment item 'sap.com_DummyClientEAR'.; nested exception is:
java.rmi.RemoteException: class com.sap.engine.services.dc.gd.DeliveryException: An error occurred during deployment of sdu id: sap.com_DummyClientEAR
sdu file path: C:\SAP\DevStudio\eclipse\workspace\DummyClientEAR\DummyClientEAR.ear
version status: NEW
deployment status: Admitted
description:
1. Error:
Cannot deploy application sap.com/DummyClientEAR. Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved...
Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved.; nested exception is:
java.rmi.RemoteException: class com.sap.engine.services.deploy.server.utils.DSRemoteException: Cannot deploy application sap.com/DummyClientEAR. Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved...
Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved.; nested exception is:
java.rmi.RemoteException: com.sap.engine.services.library_container.deploy.LCDeploymentException: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved.
at com.sap.ide.eclipse.sdm.threading.DCDeployThread.run(DCDeployThread.java:145)
-
Nested exception -
com.sap.engine.services.dc.api.deploy.DeployException: DeploymentException.
Reason: An error occurred while deploying the deployment item 'sap.com_DummyClientEAR'.; nested exception is:
java.rmi.RemoteException: class com.sap.engine.services.dc.gd.DeliveryException: An error occurred during deployment of sdu id: sap.com_DummyClientEAR
sdu file path: C:\SAP\DevStudio\eclipse\workspace\DummyClientEAR\DummyClientEAR.ear
version status: NEW
deployment status: Admitted
description:
1. Error:
Cannot deploy application sap.com/DummyClientEAR. Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved...
Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved.; nested exception is:
java.rmi.RemoteException: class com.sap.engine.services.deploy.server.utils.DSRemoteException: Cannot deploy application sap.com/DummyClientEAR. Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved...
Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved.; nested exception is:
java.rmi.RemoteException: com.sap.engine.services.library_container.deploy.LCDeploymentException: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved.
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:734)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:220)
at com.sap.ide.eclipse.deployer.dc.deploy.DeployProcessor70.deploy(DeployProcessor70.java:111)
at com.sap.ide.eclipse.sdm.threading.DCDeployThread.run(DCDeployThread.java:119)
Caused by: com.sap.engine.services.dc.cm.deploy.DeploymentException: An error occurred while deploying the deployment item 'sap.com_DummyClientEAR'.; nested exception is:
java.rmi.RemoteException: class com.sap.engine.services.dc.gd.DeliveryException: An error occurred during deployment of sdu id: sap.com_DummyClientEAR
sdu file path: C:\SAP\DevStudio\eclipse\workspace\DummyClientEAR\DummyClientEAR.ear
version status: NEW
deployment status: Admitted
description:
1. Error:
Cannot deploy application sap.com/DummyClientEAR. Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved...
Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved.; nested exception is:
java.rmi.RemoteException: class com.sap.engine.services.deploy.server.utils.DSRemoteException: Cannot deploy application sap.com/DummyClientEAR. Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved...
Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved.; nested exception is:
java.rmi.RemoteException: com.sap.engine.services.library_container.deploy.LCDeploymentException: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved.
at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:186)
at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:47)
at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:177)
at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:76)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:624)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:483)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:206)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:153)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:807)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:253)
at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:109)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:841)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:125)
at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:59)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:168)
Caused by: java.rmi.RemoteException: class com.sap.engine.services.dc.gd.DeliveryException: An error occurred during deployment of sdu id: sap.com_DummyClientEAR
sdu file path: C:\SAP\DevStudio\eclipse\workspace\DummyClientEAR\DummyClientEAR.ear
version status: NEW
deployment status: Admitted
description:
1. Error:
Cannot deploy application sap.com/DummyClientEAR. Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved...
Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved.; nested exception is:
java.rmi.RemoteException: class com.sap.engine.services.deploy.server.utils.DSRemoteException: Cannot deploy application sap.com/DummyClientEAR. Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved...
Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved.; nested exception is:
java.rmi.RemoteException: com.sap.engine.services.library_container.deploy.LCDeploymentException: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved.
at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.performDeployment(ApplicationDeployer.java:162)
at com.sap.engine.services.dc.gd.impl.GenericDeliveryImpl.deploy(GenericDeliveryImpl.java:54)
at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:157)
... 16 more
Caused by: java.rmi.RemoteException: class com.sap.engine.services.deploy.server.utils.DSRemoteException: Cannot deploy application sap.com/DummyClientEAR. Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved...
Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved.; nested exception is:
java.rmi.RemoteException: com.sap.engine.services.library_container.deploy.LCDeploymentException: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved.
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:299)
at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.performDeployment(ApplicationDeployer.java:150)
... 18 more
Caused by: java.rmi.RemoteException: com.sap.engine.services.library_container.deploy.LCDeploymentException: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved.
at com.sap.engine.services.library_container.deploy.LibraryContainer.addLibsFromClassPathElement(LibraryContainer.java:328)
at com.sap.engine.services.library_container.deploy.LibraryContainer.addLibsFromClassPathElements(LibraryContainer.java:290)
at com.sap.engine.services.library_container.deploy.LibraryContainer.getDeployableFiles(LibraryContainer.java:220)
at com.sap.engine.services.library_container.deploy.LibraryContainer.deploy(LibraryContainer.java:148)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:506)
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:248)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:215)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:371)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:405)
at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:2298)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:286)
... 19 more
<b>What can be the reason for this?</b>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Bhupesh,
It seems that you are using J2EE 1.4 EAR project for the client ear. Make sure that you have manually created a Dynamic Web 2.5 Project and that it has been included to EAR 1.5 project. From this point on start the client wizard and generate the client in the dynamic web 2.5 project. Note that you will have to manually type the name of the ear project in the wizard. It will not appear in the drop-down box for ear project selection.
Regards,
Hristo
Hi Hristo,
Thanks for your reply.
I created a dynamic web project and created a cleint from the wsdl and deployed it. but then i get the following exception, when i run the client.
javax.xml.ws.soap.SOAPFaultException: javax.ejb.EJBException: nested exception is: java.lang.RuntimeException: java.lang.NoClassDefFoundError
at com.sun.xml.ws.encoding.soap.ClientEncoderDecoder.toMessageInfo(ClientEncoderDecoder.java:84)
at com.sun.xml.ws.encoding.soap.client.SOAPXMLDecoder.toMessageInfo(SOAPXMLDecoder.java:209)
at com.sun.xml.ws.protocol.soap.client.SOAPMessageDispatcher.receive(SOAPMessageDispatcher.java:538)
at com.sun.xml.ws.protocol.soap.client.SOAPMessageDispatcher.doSend(SOAPMessageDispatcher.java:258)
at com.sun.xml.ws.protocol.soap.client.SOAPMessageDispatcher.send(SOAPMessageDispatcher.java:137)
at com.sun.xml.ws.encoding.soap.internal.DelegateBase.send(DelegateBase.java:84)
at com.sun.xml.ws.client.EndpointIFInvocationHandler.implementSEIMethod(EndpointIFInvocationHandler.java:172)
at com.sun.xml.ws.client.EndpointIFInvocationHandler.invoke(EndpointIFInvocationHandler.java:106)
at $Proxy40_10001.summitOrder(Unknown Source)
at JEE_jsp_index_1708450_1172126377496_1172133180889._jspService(JEE_jsp_index_1708450_1172126377496_1172133180889.java:64)
at com.sap.engine.services.servlets_jsp.lib.jspruntime.JspBase.service(JspBase.java:102)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:59)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:403)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:232)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:59)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:31)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:408)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:278)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:504)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:482)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:65)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:67)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:279)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:211)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:133)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:221)
I have added all the required jars in the client path.
What can be the reason behind this?
Regards
Bhupesh...
Also what s/d be the <i>'type'</i> of the Client Project which we have to test?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
98 | |
11 | |
11 | |
10 | |
10 | |
8 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.