How to use external library in EAR deployed onto J2EE engine

Question

For certain reasons some classes in .jar file in operation system level should be used in the EAR project I've deployed onto J2EE Engine.
Can some one tell me what steps I should perform to acheive this?

Answer 1

hey there,
Think im already late for this... but it may be useful to someone who reads this forum later.
I am struggling with exactly the same problem for the past more than 24
odd hours now. The sad part - Im sure I have seen this being done in a
matter of a few minutes when my team mate had an older version on NWDS.
(I am currently using SP16 NWDS). May be this indeed is a bug that SAP
needs to fix in its SP16 NWDS release.
I need to use the HSSF POI libraries for my webdynpro components and
have been trying ALL possible options given out here on SDN. To mention a
few, I have tried -
1) Jarrod's method of making a Java DC and then declaring a usage
dependency for it inside a J2EE Server (library) DC. It didnt work... it
gave me a warning that an illegal reference has been made to the runtime
public part. And the final SDA file generated in the J2EE server
component DC DIDNOT contain the jar files that I had added to the public part
of the Java DC. On investigating further, I found that there were NO
entities present in BOTH the public parts of the Java DC, even though the
folder actually contained all the required .jar files.
2) Creating an External Library DC, adding the JAR files to the
'libraries' folder. Creating two public parts, one for assembly and the second
for compilation. Then adding this DC as a 'Used DC' into a J2EE Server
(library) DC. Yet, the .sda file that is created on building the J2ee
Server (library) DC DOESNOT contain the JAR files.
3) Creating an external library DC, adding the JAR files to the
'libraries' folder. Creating two public parts, one for assembly and the second
for compilation. Then adding this DC as a 'Used  DC' into a webdynpro
DC. On building this webdynpro DC, the .ear file DOESNOT contain the JAR
files.
4) Directly adding the JAR files to my own webdynpro component in the
'src/packages' folder. This didnt work because on rebuilding the
project, the JAR files get deleted on their own.
5) Renaming my .JAR files to .ZIP, extracting the entire package
structure into folders, copy pasting this entire folder structure along with
its .class files into the src/packages folder. On rebuilding, the NWDS
deletes these folders and files on its own / behaves erratically. Also
copy pasted these .class files along with the proper package structure
into the '/bin' directory of my webdynpro application, but it still
didnt work.
The only thing that I have to try yet is to shift to SP10 of NWDS,
build this external library project and get the required JAR files put on
the wendynpro server. After that I might choose to get back onto the
SP16 version and hopefully continue productive work... !
Regards,
Navneet.