Error while starting application after deploying WebService

[former_member233677]

Hey Everyone,

I'm developing an POC with the Composition Environment SP1. I modelled a Business Object and used it within an Application Service. This one works just fine. But when I try to expose any operation of this Application Service as WebService, the application cannot be started on the server anymore.

Following error was thrown by NWDS after deploying:

-

---

2. File:C:\Documents and Settings\D043679\workspace.jdi\LocalDevelopment\DCs\demo.sap.com\poc_lr\ear\_comp\gen\default\deploy\demo.sap.com_{poc_lr}ear.ear

Name:poc_lr~ear

Vendor:demo.sap.com

Location:NetWeaver Developer Studio

Version:20070718101034

Deploy status:Warning

Version:NEW

Description:

1. Exception has been returned while the 'demo.sap.com/poc_lr~ear' was starting. Warning/Exception :

Error occurred while starting application demo.sap.com/poc_lr~ear and wait.

Reason: Clusterwide exception: server ID 11884450:com.sap.engine.services.deploy.container.DeploymentException: <Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key

at com.sap.engine.services.webservices.server.deploy.WebServicesDeployManager.prepareStart(WebServicesDeployManager.java:725)

at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:211)

at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)

at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:393)

at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:418)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:318)

at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:533)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:230)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:374)

at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:2955)

at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:2885)

at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:2861)

at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:98)

at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)

at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:31)

at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)

at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessDeplItem(DefaultDeployPostProcessor.java:70)

at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:58)

at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:646)

at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:637)

at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:488)

at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:209)

at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:154)

at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:875)

at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)

at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)

at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:61)

at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:36)

at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:882)

at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:52)

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:287)

Caused by: com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Exception occured during web services start. Unable to load type mapping registry for web service not available, application demo.sap.com/poc_lr~ear.

at com.sap.engine.services.webservices.server.deploy.ws.WSStartProcess.loadJAXBContexts(WSStartProcess.java:273)

at com.sap.engine.services.webservices.server.deploy.ws.WSStartProcess.execute(WSStartProcess.java:98)

at com.sap.engine.services.webservices.server.deploy.WSBaseAbstractDProcess.makeProcess(WSBaseAbstractDProcess.java:315)

at com.sap.engine.services.webservices.server.deploy.WebServicesDeployManager.prepareStartWebServices(WebServicesDeployManager.java:1088)

at com.sap.engine.services.webservices.server.deploy.WebServicesDeployManager.prepareStart(WebServicesDeployManager.java:721)

... 32 more

Caused by: javax.xml.bind.JAXBException: com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 1 counts of IllegalAnnotationExceptions

java.util.Collection is an interface, and JAXB can't handle interfaces.

this problem is related to the following location:

at java.util.Collection

- with linked exception:

[com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 1 counts of IllegalAnnotationExceptions

java.util.Collection is an interface, and JAXB can't handle interfaces.

this problem is related to the following location:

at java.util.Collection

]

at com.sap.engine.services.webservices.server.deploy.ws.WSStartProcess.loadJAXBContexts(WSStartProcess.java:263)

... 36 more

Caused by: com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 1 counts of IllegalAnnotationExceptions

java.util.Collection is an interface, and JAXB can't handle interfaces.

this problem is related to the following location:

at java.util.Collection

at com.sun.xml.bind.v2.runtime.IllegalAnnotationsException$Builder.check(IllegalAnnotationsException.java:66)

at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:361)

at com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>(JAXBContextImpl.java:217)

at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:76)

at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:55)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:585)

at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:210)

at javax.xml.bind.ContextFinder.find(ContextFinder.java:368)

at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:574)

at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:522)

at com.sap.engine.services.webservices.server.deploy.ws.WSStartProcess.loadJAXBContexts(WSStartProcess.java:260)

... 36 more

-

---

Does anyone has an idea how that could be fixed?

I appreciate your help!

Regards,

Michael

[former_member233677]

I discovered, that the problem is probably caused by a collection, which is returned by a findBy method.

see detail of exception:

-

---

Caused by: javax.xml.bind.JAXBException: com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 1 counts of IllegalAnnotationExceptions

java.util.Collection is an interface, and JAXB can't handle interfaces.

this problem is related to the following location:

at java.util.Collection

-

---

When I deploy an simple WS (summerizing 2 numbers) it is deployed fine and the WS is up and running.

Does anyone has experienced a similar problem? I want to expose the functionality of my BO methods in order to set up a small POC.

Can anyone please help?

Thanks & Regards,

Michael

null