Problem with pop-up window once WD application deployed to production

[Former Member]

Hi All,

I have a weird problem... We have developed a Purchase Order create application which uses a number of pop-up windows to help the user find things like vendor number and material group and similar.

The application has worked fine in both our DEV and QA systems but we went live at the weekend and since transporting the application (via the CMS / CBS) to our production portal, we have a strange problem. When we click on one of the buttons to trigger a pop-up we get the following dump:-

java.lang.NullPointerException
	at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.getViewManagerFor(ClientComponent.java:319)
	at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.<init>(WebDynproWindow.java:82)
	at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.<init>(WebDynproWindow.java:93)
	at com.sap.tc.webdynpro.clientserver.window.InternalWindow.<init>(InternalWindow.java:32)
	at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createModalWindow(ClientComponent.java:953)
	at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createWindow(ClientComponent.java:942)
	at com.atosorigin.jsg.shape.POHeaderView.onActionVendorSearch(POHeaderView.java:555)
	at com.atosorigin.jsg.shape.wdp.InternalPOHeaderView.wdInvokeEventHandler(InternalPOHeaderView.java:601)
	at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
	at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
	at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101)
	at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304)
	at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:659)
	at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
	at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251)
	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.doPost(DispatcherServlet.java:55)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code))
	at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java(Compiled Code))
	at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java(Compiled Code))
	at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java(Inlined Compiled Code))
	at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java(Compiled Code))
	at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java(Compiled Code))
	at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java(Compiled Code))
	at com.sap.engine.services.httpserver.server.Client.handle(Client.java(Inlined Compiled Code))
	at com.sap.engine.services.httpserver.server.Processor.request(Processor.java(Compiled Code))
	at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java(Compiled Code))
	at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java(Compiled Code))
	at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java(Compiled Code))
	at java.security.AccessController.doPrivileged1(Native Method)
	at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code))
	at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code))
	at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))

I can't understand why the exact same code works in DEV and QA but not PROD?! Today, I created a new activity in my NDS and assigned all of the components of the application to it then checked it in and transported it through to QA and then to PROD. This still hasn't solved the problem.

Does anyone have any ideas?

Thanks,

Gareth.

[carlos_madrid]

Hi Gareth.

I have the same thing is happening

How do I fix this?

Your reply will be very helpful to me

[Former Member]

Hi Gareth,

This may be due to the version mismatch of the production and DEV.Please check the service pack are same in both.

in the Pop-Up check all the UI element's required properties are binded the attributes.

Kind Regards,

Mukesh.

[Former Member]

Hi,

For extra info, the code that is causing the problem is:-

	public void onActionVendorSearch(
		com.sap.tc.webdynpro.progmodel.api.IWDCustomEvent wdEvent) {
		//@@begin onActionVendorSearch(ServerEvent)

		// Open a new window with the Vendor Search view in
		IWDWindowInfo windowInfo =
			(IWDWindowInfo) wdComponentAPI.getComponentInfo().findInWindows(
				"VendorSearchPopup");
		IWDWindow window =
			wdComponentAPI.getWindowManager().createWindow(windowInfo, true);
		window.setWindowPosition(400, 50);
		window.open();
		wdContext.currentVendorSearchPopupElement().setWindowInstance(window);
		//@@end
	}

The IWDWindow window =... line seems to be the one causing the problem, as if the WD framework can't get the Window Manager. Anyone seen this before as I simply can't fix it!

Thanks,

Gareth.