Good old NullPointerException

[Former Member]

Hi, all!

I successfully deployed a local Web Dynpro DC developed on another system at my J2EE-engine. After maintaining the JCo-Connections, I receive the following error:

java.lang.NullPointerException
at com.sap.tc.webdynpro.progmodel.context.MappingInfo.getDataNode(MappingInfo.java:78)	at com.sap.tc.webdynpro.progmodel.context.MappedNodeInfo.getDataNode(MappedNodeInfo.java:199)
at com.sap.tc.webdynpro.progmodel.context.MappedNodeInfo.getStructureType(MappedNodeInfo.java:108)
at com.sap.tc.webdynpro.progmodel.context.MappedNodeInfo.getStructureType(MappedNodeInfo.java:109)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initStructureType(NodeInfo.java:688)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initAfterCompletedMapping(NodeInfo.java:676)
at com.sap.tc.webdynpro.progmodel.context.MappingInfo.getDataNode(MappingInfo.java:83)
at com.sap.tc.webdynpro.progmodel.context.MappingInfo.initMapping(MappingInfo.java:121)
at com.sap.tc.webdynpro.progmodel.context.MappingInfo.init(MappingInfo.java:117)
at com.sap.tc.webdynpro.progmodel.context.MappedNodeInfo.doInit(MappedNodeInfo.java:207)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:654)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:657)
at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:436)
at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:374)
at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:403)
at com.sap.tc.webdynpro.progmodel.context.MappingInfo.getDataNode(MappingInfo.java:79)
at com.sap.tc.webdynpro.progmodel.context.MappingInfo.initMapping(MappingInfo.java:121)
at com.sap.tc.webdynpro.progmodel.context.MappingInfo.init(MappingInfo.java:117)
at com.sap.tc.webdynpro.progmodel.context.MappedNodeInfo.doInit(MappedNodeInfo.java:207)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:654)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:657)
at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:347)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:370)
at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:608)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:248)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
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:100)	at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

Has anybody got any idea what could be the reason for that?

Thanks a lot in advance!

Regards,

Thomas

[Former Member · Accepted solution]

Hi Thomas,

The reason is: It occurs when the ClassLoader of a DC is null.

What SP level you are in??.

/Raj.

[Former Member · Accepted solution]

Hi, Raj!

Thanks for your answer!

Our system runs on SP 15, but I' m not quite sure if this is the same SP-level the DCs were originally developed on.

Regards,

Thomas

[Former Member · Accepted solution]

Hi Thomas,

as I mentioned please check your mappings once again...carefully...ASAIK...SP9 overcomes this problem...

/Raj.

[Former Member · Accepted solution]

Hi Thomas,

Is your local engine SP15 as well?

Never use a a higher version of NWDS than the version of WAS.

Check it??

Lokesh

[Former Member · Accepted solution]

Hi Thomas,

Is your local engine SP15 as well?

Never use a a higher version of NWDS than the version of WAS.

Check it??

Lokesh

[Former Member · Accepted solution]

Hi, Raij!

The DCs were developed on Web AS 6.40 SP 13 and are now deployed on SP 15.

Regards,

Thomas

[Former Member · Accepted solution]

Thomas,

Usually WD runtime is quite tolerant to applications created with lower version of IDE, however, to make things clear, it is better to re-build application with same version SP15.

Next, if your mapping is set between 2 components (via Used DC) you may try the following trick: create an empty method in used component, and invoke it from wdDoInit of component controller of embedder. I saw several times that mapping (especially reverse mapping) does not cause used components to be initialized completely.

VS

Message was edited by: Valery Silaev

[Former Member · Accepted solution]

Hi, Valery!

I rebuilt the app within my dev environment and also created an method within wd component interface controller of comp1 which I call in using comp2. Unfortunatly I still get the error.

Any more ideas?

Thanks in advance!

Regards,

Thomas

[Former Member · Accepted solution]

Hi, Lokesh!

Yes, both NWDS and WAS are of SP15.

Regards,

Thomas