cancel
Showing results for 
Search instead for 
Did you mean: 

Missing type in context mapping during migration from 7.0 to 7.31

Former Member
0 Kudos

Hello experts.

We are migrating all our projects from 7.0 to 7.31 and we are facing an issue (again).

We have to migrate DCs we didn't develop and there are some compilation problems.

The main DC uses some interface projects:

http://i.imgur.com/e7z54fh.jpg

We can't build it because of an error in SearchParams view.
Looking for the cause we've seen that the context mapping with the interface is broken because of this error:

[wdgen] Caused by: java.lang.IllegalStateException: assertion failed: metamodel inconsistency: data type is null

The context mapping:

http://i.imgur.com/O5s8QaS.png

but the DC of the interface has no error in building and the context is ok, data type are not missing:

http://i.imgur.com/tJGr3Df.jpg

We already tried to repair internal Web Dynpro API usage, project structure & classpath, migrate context tree as suggested by NWDS but with no luck.

If it can help you can see the build.log file attached to this post.

Thanks for your help.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Loic,

Have you done a complete component migration or just a normal migration without component migration in NWDS ?

I am not sure the screenshots are from 70X environment or 731. Ideally such context mapping shouldnt break after normal automated migration, which doesn't involve component migration using cheat sheets.

Assuming the error you show in context mapping in 70x environment.

1. Check if the Component to which f4part* inteface view belongs, if there's any error. Ideally you can rebuild it and check if there are any error.

2. Check the public parts of the f4part* to check  if the the context are properly exported.

3. one trivial solution will be delete all and build again  by  doing a project clean.

see if it works

Satyajeet

Former Member
0 Kudos

Hello !

Thank you for your reply, it was very helpful. This was indeed an issue with public parts.

We found the solution by comparing our project to existing working ones (I mean successfully migrated ones) and there was a problem with public parts exposed by all 3 DC. They didn't expose their "model" and adding them to public parts solved our problems.

Thanks again.

Answers (0)