Can't wrap External Library DC project.

[Former Member]

Hi all,

I do these procedure:

1. create a External Library DC, 
2. then create two public part : compilation and assembly, 
3. add jars to the two public part
4. build dc

5. Create a second DC of type web dynpro
6. add used DC  compilation and assembly
7. write my test code use jars added in step 3
8. build DC
9,deploy

After deploy and view in EP, my web dynpro DC can't find jars added by External Library.

And i can't find external jars in deployed ear file.

My NW is 7.0 SP9, if someone know which step i have missed.

best regard

[Former Member]

Hi,

You can try to deploy the External Library Project using the J2EE Server Library type DC, and use the public part of this DC in Web Dynpro DC.

You'll also need to define the Server Library component in the

DC Properties -> Project References -> Library References of the Web Dynpro DC.

For detailed procedure you can follow [this|https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/2361] [original link is broken] [original link is broken] [original link is broken]; blog.

Regards,

Alka.

[Former Member]

hi Alka,

i did the procedure follow the blog, but still not success.

There is some difference. When i add jars to public part in External Library DC, it do not create ExternalLibs auto, but info creating public part of two choice:

1. provides an API for developing/compiling other DCs

2. can be package into other build result(e.g.SDAs)

and i try the all two choice and add it to u201CJ2EE Server / Libraryu201DDC, it can't succeed. i can not find jars in sda file. jars contained were null when see the "J2EE Server /Library" in visual administrator.

best regard.

reefish

[former_member185086]

Hi

One question : In NW is 7.0 SP9 there is any provision to publish file as archive or file.

(select library -- select jar file right click-- select development component)

If yes then do the same procedure as u mentioned in question for publish as archive.

Best Regards

Satish Kumar

[Former Member]

I believe this is a bug in SP9.