Skip to Content
author's profile photo Former Member
Former Member

bugs & code generation problems (Sneak Preview II) !


We have built some larger Web Dynpro projects (containing multiple wd components) and are regularly experiencing major problems, that we unfortunately can't reproduce (yet?)

The problem often starts with some inconsistency in the code. E.g. corrected changes are always undone, as soon as the meta data is saved. The only a rebuild and/or a restart of NDS seems to help.

But.. later on code for the wd component having the problems before, isn't being (re)generated anymore. Actually the \gen_wdp\<component> package does exist anymore at all, nor is it being re-generated.

However, for the other components (re)generation works fine; even if their \gen_wdp\ packages are empty.

The only solution that works in (most) cases, is to start all over again with a recent copy of such an corrupted (?) wd component. We takes LOTS of time :(((

Rebuild nor Repair (project level or component level)seems to help.

Our question: can we force a total rebuild in some way or solve such code generation problems in any other way?

Any tips would we really appreciated!!



Add comment
10|10000 characters needed characters exceeded

1 Answer

  • Posted on Apr 28, 2004 at 09:54 AM

    Hi Rob,

    I donĀ“t know if this is the same problem I had several times yet.

    In my case the complete controller code is commented. To be exactly my custom code is commented. The code generated by the Web Dynpro plugin has gone completely.

    My solution for this:

    - delete all files and subdirs from gen_* directories.

    - closing all projects in NDS.

    - restarting NDS.

    After that the source is generated again.



    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Rob and Helmut,

      this problem exists for a very long time actually with different possible reasons (some versions failed generating if you didn't bind a context attribute to a DropDownByKey element for example). Since the reasons aren't really reproducable, it's difficult to determine why this happens sometimes. Anyway, no editing or changing action in the NDS should lead to this, simply stopping at the "point of no return" would be better since one could check where and possibly why this happens.