Transporting "External Library"-DC from Development to Consolidation

[Former Member]

Hello,

we have a problem when transporting DCs from the development to the consolidation system. There are two DCs involved:

One is an "External Library"-DC ("doclibs") which contains only two jars. This DC provides two public parts (PP) for purposes compilation ("compLibsPP) and assembly.

The other DC ("docwriter") accesses the doclibs-DC via the compLibsPP with setting the used DC as required for build time and runtime.

After importing the compartment in the Consolidation, the CBS fails when building "docwriter" with an error at the DC Model check (the "doclibs"-DC has been imported successfully before):

Development Component Build (2006-03-24 10:09:45)

Component name: erg/zms/fallbackwriter/docwriter

...

DC Model check: [dcmake] All used DCs are available locally

[dcmake] ERROR: Check for used DCs Failed: Could not find used public part "compLibsPP" ...

[dcmake] Build failed with errors

I tried another attempt:

Removing the access to compLibsPP and therefore adding a Used DC that references the "doclibs"-DC completly (not only an individuals Public Part).

Now the Model check succeeds, but afterwards the compiler cannot resolve the package- and symbol names of the imported classes from the doclibs.

In the development system, we have no problem with the build process.

Is anyboby there, who knows this Problem? Thanks for help!

Stefan

[Former Member]

First of all: It makes no sense defining a runtime dependency to an External Library DC, since this DC-type does not have a deployable result.

If you need the jars contained in an External Library DC at runtime, you must:

- Define a J2EE DC that has an entity reference to the public part for assembly of the External Libary DC and deploy that J2EE library

or

- Create an entity reference to the public part for assembly of the External Libary DC in the using DC.

In the first case the jars will exist in only one place on your runtime systems. In the second case they will be there as many times as you encapsulate them in using DCs.

Concerning your build problems:

Are your NWDS and NWDI on the same SP level? It seems like your NWDS is at a higher level, which allows you to create DCs that your NWDI does not understand.

[Former Member]

Hi Pascal:

You can find the deployable file of an external library project dc in the perspective navigator ---> look for the package: gen/default /deploy/*.sda

Right click and you can see de deploy action.

Rocío.

[Former Member]

You replied to a thread that is over 1,5 years old...