Skip to Content
0
Jun 04, 2018 at 07:37 PM

Problem maintaining a source code of the Java mapping in NWDI

122 Views

This is a two part question.

We've developed a Java mapping and need to preserve the source code somewhere, so we chose to create a Java development component in our project software component, along with a BPM project that is in the same software component.

Java mappings use AbstractTransformation. NWDS contains with the necessary dependencies to compile a class that extends the above. However, when we build the activity that contains a class that extends the above in NWDI, it fails, because NWDI is unable to find the dependencies. This is the first question - how do we make NWDI find the necessary dependencies?


The second issue that we are having is with the basic workaround that we have achieved for the above. We have commented the code out and commit just the comment to NWDI to compile. This resolves the dependency issue and does not cause any runtime issues since this code is not given to NWDI to create a runtime component. Instead it is promoted manually as a JAR, exported from NWDS, into ESR, and then it is promoted up to other environments as an ESR object. Here is the issue: NWDI is stuck trying to compiling an outdated version of this sources code, before it was commented out! No matter what changes we send up, it always tries to compile an outdated version. Is there some kind of cache in NWDI that can be refreshed? How can we force it to compile the latest changes?