cancel
Showing results for 
Search instead for 
Did you mean: 

External Library DC in NW2004s SP09

Sigiswald
Contributor
0 Kudos

Hello,

Unfortunately I have a problem while trying to use an External Library DC in a Web Dynpro DC. I do exactly as described in <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/5a/2e2f4234135433e10000000a155106/content.htm">External Library DC</a>. I did this many times before on NW2004 SP15 and NW2004 SP18, but on NW2004s SP09 it doesn't work anymore. My Web Dynpro DC does compile, but the jar files of the External Library are not deployed (as part of the generated WD ear file).

Just what I did in more detail:

1. create a DC of type External Library

2. added a jar file in the libraries directory

3. created a public part with purpose compilation

4. created a public part with purpose assembly

5. created a DC of type Web Dynpro

6. added a Used DC reference to both public parts of the External Library where I use twice the Build Time Dependency Type

Compilation succeeds, but since the jar file of the External Library DC is not included in the generated ear file of the Web Dynpro DC, I get a ClassNotFoundException at runtime.

The (generated) buildDeployArchive.xml (in the ./_comp/gen/default/logs directory) on NW2004 SP18 looks something like:


...
<target name="packDeployArchive">
  <timer/>
  <taskdef name="srcpacker" classname="com.sap.tc.buildplugin.pp.ant.SourceArchiveCreatorTask"/>
  <srcpacker destination="C:DATANWDS2004SP18.dtcLocalDevelopmenttACBC66A31AAF98F274753FD876A95444sdasrcjavasrc.zip" archiveLocation="srcarchive">
    <UsedPublicPart root="C:DATANWDS2004SP18.dtcLocalDevelopmentDCssap.comsaplib_compgendefaultpubliclib-assembly"/>
    <UsedPublicPart root="C:DATANWDS2004SP18.dtcLocalDevelopmenttACBC66A31AAF98F274753FD876A95444wda-pp"/>
  </srcpacker><timer message="Source archive creation finished in "/>
...

whereas on NW2004s SP09 it looks something like:


...
<target name="packDeployArchive">
  <timer/>
  <srcpacker destination="C:DATANWDS2004sSP09.dtc0t2C1310EDE50928B0B2FB8E7B4A6B781Csdasrc.zip" archiveLocation="srcarchive">
    <UsedPublicPart root="C:DATANWDS2004sSP09.dtc0t2C1310EDE50928B0B2FB8E7B4A6B781Cwda-pp"/>
  </srcpacker>
...

In NW2004s SP09 it does not contain a UsedPublicPart element that refers to lib-assembly. Of course I double checked, among other things, the lib-assembly public part really has the purpose assembly. Now I'm pretty sure the behaviour of the External Library DC in combination with a Web Dynpro DC has changed. Should this be considered a bug?

Does anyone has the same experience on NW2004s (SP09)?

tnx!

/Sigiswald

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Sigiswald,

well it seems SAP also considers that a bug, if you go to the Service marketplace -> Support Packages and Patches -> SAP NetWeaver -> SAP NETWEAVER -> SAP NETWEAVER 2004S -> Entry by Component -> Development Infrastructure, there is a SAP_BUILDT SP09 Patch 1 referring to note 993799 which says:

"Jar files, especially from development components with type "External Library" are not assembled into the WDA archive for Web Dynpro development components."

Are you using the original SP09 version or this patch?

Regards,

Marc

Sigiswald
Contributor
0 Kudos

Thanks Marc!

This note was exactly what I was looking for.

We're indeed still using the original version (patch level 0) of the SAP_BUILDT SC.

Kind regards,

/Sigiswald

Answers (0)