Exception While Developing FPM application.

[Former Member]

Hi All,

We are on EP7.0/ECC6.0.

I'm trying to develop a new ESS webdynpro application using FPM. I'm using the steps as given <a href="http://help.sap.com/saphelp_erp2005/helpdata/en/43/3b709efa6c1bcbe10000000a1553f7/frameset.htm">here</a>

The application throws following exception while doing 'deploy new archive and run' from developer studio.

java.lang.NoSuchMethodError: com.sap.pcuigp.xssfpm.java.ApplicationContext.isSplitupApplication()Z

at com.sap.pcuigp.xssutils.ccxss.CcXss.loadConfiguration(CcXss.java:214)

at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXss.loadConfiguration(InternalCcXss.java:153)

at com.sap.pcuigp.xssutils.ccxss.CcXssInterface.loadConfiguration(CcXssInterface.java:112)

at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXssInterface.loadConfiguration(InternalCcXssInterface.java:124)

at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXssInterface$External.loadConfiguration(InternalCcXssInterface.java:184)

Full Exception trace is:

java.lang.NoSuchMethodError: com.sap.pcuigp.xssfpm.java.ApplicationContext.isSplitupApplication()Z

at com.sap.pcuigp.xssutils.ccxss.CcXss.loadConfiguration(CcXss.java:214)

at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXss.loadConfiguration(InternalCcXss.java:153)

at com.sap.pcuigp.xssutils.ccxss.CcXssInterface.loadConfiguration(CcXssInterface.java:112)

at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXssInterface.loadConfiguration(InternalCcXssInterface.java:124)

at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXssInterface$External.loadConfiguration(InternalCcXssInterface.java:184)

at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:190)

at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)

at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)

at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)

at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:707)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:269)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:759)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:712)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:261)

at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)

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

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)

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)

It also gives Correction Hints as:

Correction Hints

The currently executed application, or one of the components it depends on, has been compiled against class file versions that are different from the ones that are available at runtime.

If the exception message indicates, that the modified class is part of the Web Dynpro Runtime (package com.sap.tc.webdynpro.*) then the running Web Dynpro Runtime is of a version that is not compatible with the Web Dynpro Designtime (Developer Studio or Component Build Server) which has been used to build + compile the application.

Note: the above hints are only a guess. They are automatically derived from the exception that occurred and therefore can't be guaranteed to address the original problem in all cases.

......................................................................................................................

I have verified that NWDS and NWDI are on same level.

Any ideas how to resolve this??????

cheers~

avadh

[Former Member · Accepted solution]

Hi ,

I guess you have some lline..

with

getApplicationContext().isSplitUpApplication();

.

Are the versions of SCA s in NWDI ( i.e xssutils) which you have referenced in ur component.. and the ones deployed in your webAs java server .. the same ?

It seems to be a mismatch.. or the reference declaration might be jus build time .. something like that .. ?

Regards

Bharathwaj

[Former Member · Accepted solution]

Hi Bharathwaj ,

Have checked the versions of SCAs, both places its PCUI_GP 600 SP8.

I resolved this issue by removing the dependencies 'deploy time' and 'run time', and keeping only 'build time' for DCs xssfpm and xssutils.

My fear now is that by removing these dependencies, can it result into some other errors(broken DCs etc) in CBS while we try to build and release these activities?

cheers~

avadh

[Former Member · Accepted solution]

Hi.

If you are sure that the versions are same in both places.. I dont see it occurring.. !

Thanks and Regards

Bharathwaj

[Former Member · Accepted solution]

Yupp,

Thts what my EP administrator told me. Verified both the versions from componentInfo and Consolidation tab in Transport studio.

Is it correct way?

cheers~

avadh

[Former Member]

Yep.. For your satisfaction , you can open a standard component and check if they have declared the same dependencies

Regards

Bharathwaj

[Former Member]

Hi Avadh,

Did you sync ed the DC's. Synch sources and used DCs. Try this.

Thanks,

Raags

[Former Member]

Hi Raags,

Thts already done.

cheers~

avadh