Generation error during WebDynpro migration from 7.0 to 7.31

[michael_voss2]

Hello everybody!

We are trying to migrate some WebDynpro DCs to NW 7.31. After checking in the old sca file into the new track, synching the DCs in NWDS and creating projects for them, most of the DCs compile ok, but we get a build error in one WebDynpro DC we are not able to resolve.

The build.log shows

    [wdgen] [Error]   Generation error while processing <somepath>/NWDSWorkplace_7_3.jdi/2/t/C5FB4D1181864A07E2DF8F1E8D280266/gen_wdp/packages/de/xxx/somepath/wdp/Resource<myview>.properties (java.lang.reflect.InvocationTargetException)

with the stack trace showing an Generation error while processing template defaultResource:

     [wdgen] [Info]    Generation error while processing template defaultResource

     [wdgen] [Info]    Catching throwable null

     [wdgen] [Info]    java.lang.reflect.InvocationTargetException

     [wdgen] at sun.reflect.GeneratedMethodAccessor114.invoke(Unknown Source)

     [wdgen] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

     [wdgen] at java.lang.reflect.Method.invoke(Method.java:597)

     [wdgen] at com.sap.ide.generationfwk.task.GenerationTaskJavaMethod.executePersistent(GenerationTaskJavaMethod.java:139)

     [wdgen] at com.sap.ide.generationfwk.GenerationBase.doPersistentGeneration(GenerationBase.java:207)

     [wdgen] at com.sap.ide.generationfwk.GenerationBase.doPersistentGeneration(GenerationBase.java:164)

     [wdgen] at com.sap.ide.webdynpro.generation.Generation.doPersistentGenerationForComponentDefaultResource(Generation.java:541)

     [wdgen] at com.sap.ide.webdynpro.generation.Generation.doPersistentGenerationForComponentResources(Generation.java:3188)

     [wdgen] at com.sap.ide.webdynpro.generation.Generation.doPersistentGenerationForComponentRecursively(Generation.java:1788)

     [wdgen] at com.sap.ide.webdynpro.generation.Generation.doPersistentGenerationForComponentRecursively(Generation.java:1772)

     [wdgen] at com.sap.ide.webdynpro.generation.Generation.doPersistentGenerationForComponentRecursively(Generation.java:1772)

     [wdgen] at com.sap.ide.webdynpro.generation.Generation.generateComponentsForArchive(Generation.java:2660)

     [wdgen] at com.sap.ide.webdynpro.generation.Generation.generateMDOsForArchive(Generation.java:2604)

     [wdgen] at com.sap.ide.webdynpro.generation.Generation.generatePersistentArchive(Generation.java:1630)

     [wdgen] at com.sap.ide.webdynpro.generation.console.GenerationConsole.generate(GenerationConsole.java:190)

     [wdgen] at com.sap.webdynpro.generation.ant.GenerationAnt.main(GenerationAnt.java:69)

[...]

So far, everything I could find is pointing to some localisation issue, but I'm not able to solve the problem. Some hints say I'd have to change the language settings of the DC (or SC) upon import, but I never saw anything that gave me an opportunity to do so. On the other hand, other WebDynpro DCs in the same track get imported o. k. and compile without any error.

The other thing I see in this WebDynpro DC is that in some views, all GUI element texts are missing, some views are o. k.

Can anyone shed some light on this issue ?

Thanks

Michael

[Former Member · Accepted solution]

Dear Michael,

Did you check in component properties perspective for Language?

Thanks & Regards,

Patralekha

[michael_voss2 · Accepted solution]

Hi Patralekha,

The "Language" property of this DC is set to "American English", and the "oroginalLocale" property of the "localization" branch in the Custom Properties page is set to "en". Funny enough, the exact same settings of another WebDynpro DC in the same track do not issue any error during build time or runtime.

If I'd want to change the localization settings, where would I find them ?

Thanks

Michael

[michael_voss2 · Accepted solution]

Ok, I can provide some more information:

In the WebDynpro DC's .dcdef file, I changed

<properties>

  <localization xmlns="http://xml.sap.com/2003/06/Localization" xmlns:ns0="http://xml.sap.com/2003/06/Localization">

   <domain>BC</domain>

   <originalLocale>en</originalLocale>

  </localization>

  <minimizeClassFiles xmlns="http://xml.sap.com/2004/07/DCProperties/WebDynpro" xmlns:pns1="http://xml.sap.com/2004/07/DCProperties/WebDynpro">auto</minimizeClassFiles>

  <projectVersion xmlns="http://xml.sap.com/2004/07/DCProperties/WebDynpro">1</projectVersion>

</properties>

to

<properties>

  <localization xmlns="http://xml.sap.com/2003/06/Localization" xmlns:ns0="http://xml.sap.com/2003/06/Localization">

   <domain>BC</domain>

   <originalLocale>de</originalLocale>

  </localization>

  <minimizeClassFiles xmlns="http://xml.sap.com/2004/07/DCProperties/WebDynpro" xmlns:pns1="http://xml.sap.com/2004/07/DCProperties/WebDynpro">auto</minimizeClassFiles>

  <projectVersion xmlns="http://xml.sap.com/2004/07/DCProperties/WebDynpro">1</projectVersion>

</properties>

After that, the views with previously missing GUI texts were showing these texts inside the NWDS WebDynpro view editor, and those views that did previously show these text didn't show them any more! So there seems to be some discrepancy regarding the language the views were created in.

Any hint on what files have to be changed in what way to either remove internationalization completely or to set all views to a single language ?

Thanks

Michael

[michael_voss2 · Accepted solution]

Ok, I finally found a solution to my problem.

In the "old" 7.0-DC, it looks like some of the views have been created with standars locale "en" and some of them with standard locale "de". After migrating the DC to 7.3, the DC itself got supplied with an "originalLocale" that gets set to "en" automatically. Thus, the development environment tried to lookup the standard .xlf files, which were only partially set to the correct language ("en"). Those views with such a file showed the GUI texts, those without didn't.

What I finally did to solve the problem was checking out all files of the DC into an NWDI activity, closing NWDS and replacing "en" in all files with "de" (including the quotation marks (!!!), I guess the other way around this would work, too, as well as with any other locale) and saving these files. After re-opening NWDS, all GUI texts were present and the DC compiled just fine!

Regards

Michael

[maarten_duits2 · Accepted solution]

Hello Michael,

I am in the middle of a migration from 7.0 to 7.4 and have the same Build error as described above. Unfortunately  my knowledge of Webdynpro Java isn't that great. With the answer you provided I can't solve this issue. I was hoping you could provide me with some extra guidelines to solve this issue.

Thanks in advance.

Kind regards,

Maarten.

[michael_voss2 · Accepted solution]

Hello Maarten!

Check the files that your application consists of (migrated version, NW7.4) for inconsistencies regarding the locales. The files reside in the <your_eclipse_workspace_folder>/<component_number>/DCs/<your_prefixes>/<your_webdynpro_development_component_name>/_comp/src/packages/<your_package_structure>/

on your local NWDS workstation (for me it's E:\NWDS\eclipse\workspace.jdi\0\DCs\mycompany.com\myprefix\mywebdynpro\_comp\src\packages\wdp

Most of the files your WebDynpro consists of are xml files, sometimes containing Java code inside of [CDATA[//]].sections. In the enclosing xml of the *.wdcontroller and *.wdcontroller.xlf files, you can find something like 'masterLanguage="nl"' or 'originalLocale xml:lang="en"'. If your WebDynpro is internationalized, you'll propably find some more filetypes with this kind of information. Except these I18n files, try setting the language inside these xml files to the same locale as in the "ProjectProperties.wdproperties" file in the parent directory without using NWDS. Remember to save the unchanged files to a secure place before you check out all files into a new activity (it's important to use a new activity) you create in NWDS. Close NWDS and use an external editor. Reopen NWDS and try to build your component. Do not check in this activity until everything works fine. Do not change anything else in this activity so you will be able to revert and delete this activity once something goes wrong. If you want to change something else, close NWDS and use your (external but capable) editor.

Maybe you'll have to play around with the locales, but if your error is related to this, you'll possibly be able to build successfully. I messed up a lot of things with this at first, so be sure not to check in anything until you are sure that this problem is solved. Restore the files from your backup copies, revert the activity and delete it once you have to restart. It took quite a while to sort this out, so be patient and careful.

feel free to follow up on this at any time...

Regards

Michael

[maarten_duits2 · Accepted solution]

Hello Michael,

Thanks for the detailed description!! Unfortunately i still didn't solve the problem. I searched al the files and didn't find a file with different language setting.

Kind regards,

Maarten