Metamodel version validation when compiling Processes

[michael_chytracek3]

Hi Experts,<br>

<br>

After upgrading Developer Studio to 7.3 SP07 PAT0000 (latest available from SAP update site) and compiling our BPM Processes we get Build errors complaining about "Metamodel version validation...". We buildt up a fresh workspace and downloaded all Projects and dependent Libs from the NWDI Server. The dependent Libs on the server are also the latest available version (7.3 SP5 PAT??? i think)<br>

A similar simple process compiles well in a Local Development Configuration so we think that the dependent libs in the NWDI track are not compatible with the generated process definitions by the Developer Studio. Can this be true?<br>

<br>

<br>

[MOINInit] Meta models found.<br>

[MOINInit] Referenced meta-model: D:\workspace.jdi\0\DCs\sap.com\ide\es\config\mc\model\bi\_comp\gen\default\public\MM_Inf\lib\moin\sap.com_idees_configmc~model_xmi.zip<br>

[MOINInit] Referenced meta-model: D:\workspace.jdi\0\DCs\sap.com\tc\bpem\bi\model\flow\_comp\gen\default\public\MM_Inf\lib\moin\glx~ide_xmi.jar<br>

[MOINInit] Referenced meta-model: D:\workspace.jdi\0\DCs\sap.com\tc\bpem\bi\model\triggernet\_comp\gen\default\public\MM_Inf\lib\moin\glx~tnet_xmi.jar<br>

[MOINInit] Referenced meta-model: D:\workspace.jdi\0\DCs\sap.com\tc\esmp\bi\model\wsdl20\_comp\gen\default\public\MM_Inf\lib\moin\sap.com_tcesmp_modelwsdl20_xmi.zip<br>

[MOINInit] Referenced meta-model: D:\workspace.jdi\0\DCs\sap.com\tc\esmp\bi\model\xsd1\_comp\gen\default\public\MM_Inf\lib\moin\sap.com_tcesmp_modelxsd1_xmi.zip<br>

[MOINInit] Referenced meta-model: D:\workspace.jdi\0\DCs\sap.com\tc\mie\bi\model\gfw\_comp\gen\default\public\MM_Inf\lib\moin\sap.com_comsap_migfw_mmdef_assmbl.zip<br>

[MOINInit] Referenced meta-model: D:\workspace.jdi\0\DCs\sap.com\tc\moin\bi\model\textverticalization\_comp\gen\default\public\MM_Inf\lib\moin\sap.com_tcmoin_modeltextverticalization_xmi.zip<br>

[MOINInit] Referenced meta-model: D:\workspace.jdi\0\DCs\sap.com\tc\moin\bi\model\util\_comp\gen\default\public\MM_Inf\lib\moin\sap.com_tcmoin_modelutil_xmi.zip<br>

[MOINInit] DataArea name: DefaultDataArea<br>

[MOINInit] Moin initialized in 1654 milliseconds.<br>

[BpemTask] BC-BMT-BPM-SRV com.sap.tc.glx.BpemTask execute() - Metamodel version validation...<br>

Caused by:<br>

java.lang.NullPointerException<br>

at com.sap.tc.glx.BpemTask.metaModelVersionCheck(BpemTask.java:549)<br>

at com.sap.tc.glx.BpemTask.execute(BpemTask.java:96)<br>

at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)<br>

at sun.reflect.GeneratedMethodAccessor123.invoke(Unknown Source)<br>

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)<br>

at java.lang.reflect.Method.invoke(Method.java:597)<br>

at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)<br>

at org.apache.tools.ant.Task.perform(Task.java:348)<br>

at org.apache.tools.ant.Target.execute(Target.java:357)<br>

at org.apache.tools.ant.Target.performTasks(Target.java:385)<br>

at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)<br>

at org.apache.tools.ant.Project.executeTarget(Project.java:1306)<br>

at com.sap.tc.buildplugin.ant.util.AntRunner.run(AntRunner.java:115)<br>

at com.sap.tc.buildplugin.DefaultAntBuildAction.execute(DefaultAntBuildAction.java:53)<br>

at com.sap.tc.buildplugin.DefaultPlugin.processSequence(DefaultPlugin.java:235)<br>

at com.sap.tc.buildplugin.DefaultPlugin.handleBuildStepSequence(DefaultPlugin.java:174)<br>

at com.sap.tc.buildplugin.DefaultPlugin.performBuild(DefaultPlugin.java:165)<br>

at com.sap.tc.buildplugin.DefaultPluginV3Delegate$BuildRequestHandler.handle(DefaultPluginV3Delegate.java:66)<br>

at com.sap.tc.buildplugin.DefaultPluginV3Delegate.requestV3(DefaultPluginV3Delegate.java:48)<br>

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)<br>

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)<br>

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)<br>

at java.lang.reflect.Method.invoke(Method.java:597)<br>

at com.sap.tc.buildtool.v2.impl.PluginHandler2.maybeInvoke(PluginHandler2.java:403)<br>

at com.sap.tc.buildtool.v2.impl.PluginHandler2.request(PluginHandler2.java:149)<br>

at com.sap.tc.buildtool.v2.impl.PluginHandler2.build(PluginHandler2.java:87)<br>

at com.sap.tc.buildtool.PluginHandler2Wrapper.execute(PluginHandler2Wrapper.java:59)<br>

at com.sap.tc.devconf.internal.DCProxyMake.make(DCProxyMake.java:276)<br>

at com.sap.tc.devconf.internal.DCProxy.make(DCProxy.java:1459)<br>

at com.sap.tc.devconf.internal.DCProxy.make(DCProxy.java:1441)<br>

at com.sap.tc.devconf.internal.DCProxy.make(DCProxy.java:3927)<br>

at com.sap.ide.dii08.internal.commandz.BuildDcsCommand.build(BuildDcsCommand.java:333)<br>

at com.sap.ide.dii08.internal.commandz.BuildDcsCommand.execute(BuildDcsCommand.java:176)<br>

at com.sap.ide.dii08.internal.service.CommandExecutor$2.run(CommandExecutor.java:77)<br>

at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)<br>

at com.sap.ide.dii05.util.internal.lock.DiiConsistencyServiceImpl.executeConsistentWorkspaceRunnable(DiiConsistencyServiceImpl.java:90)<br>

at com.sap.ide.dii05.util.internal.lock.DiiConsistencyServiceImpl.executeConsistentWorkspaceRunnable(DiiConsistencyServiceImpl.java:52)<br>

at com.sap.ide.dii08.internal.service.CommandExecutor.executeInWorkspaceAndDevConfLocks(CommandExecutor.java:90)

at com.sap.ide.dii08.internal.service.InternalDiiCommandService.buildDcs(InternalDiiCommandService.java:179)<br>

at com.sap.ide.dii08.internal.service.InternalDiiCommandService.buildDcs(InternalDiiCommandService.java:986)<br>

at com.sap.ide.dii05.ui.internal.actions.dc.BuildAction$2.run(BuildAction.java:193)<br>

at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)<br>

Edited by: Michael Chytracek on Feb 18, 2012 9:37 AM

[Former Member]

Hi

I'm facing the exactly same problem with NWDS 7.3 SP7.

I switched back to NWDS 7.3 SP5 the CAF generation and building works well now.

Best regards

Klaudio

[junwu]

why you update your nwds? did you update the track also?

[michael_chytracek3]

We updated the nwds from SP5 to SP7 because of a bug in nwds (cannot set a principal from the UME of the connected Java Stack).<br>

After this we imported the latest Service pack libs into the track and transported them through the track.<br>

After this we updatetd the track in nwds. <br>

Is there other upgrading to do?<br>

<br>

Regards<br>

Michael

[junwu]

it should be enough, but in your first post, you say the track is in sp5.

[michael_chytracek3]

Yes, our SAP infrastructure told us that the latest available SP for 7.3 is somewhat SP5 Patxxxx and that there is nothing newer out there (such as SP7). I he wrong?

[junwu]

if your nwds is sp7, your server has to be the same version. the SC should also has the same version of dependent SCA in the track.

[michael_chytracek3]

John,<br>

<br>

I do not think that it is essential to have the same SP in both the track libs and nwds, especially SP7 is planned by April (week 14) by SAP for Netweaver 7.3<br>

<br>

Any idea what could be the problem? Do you know where to find the metamodel version in the generated sources?<br>

<br>

Regards<br>

Michael

[junwu]

why do you think like that?

the lib in your nwds is downloaded from the track. how can they be different?

if your server is not upgraded, you'd better stay with the old version of nwds.

[joao_sousa2]

This model is weak at best, because NWDS works with automatic updates and server obviously has to be upgraded.

I have the same error and in fact my NWDS is SP07 and my server is SP06 but when I installed NWDS the SP07 wasn't even out yet. So NWDS upgrades and I lose access to NWDI? This makes no sense.