|
Re: shared lib [message #187700 is a reply to message #187683] |
Wed, 07 February 2007 15:51 |
Eclipse User |
|
|
|
Originally posted by: kosta.bea.com
What I typically do in this situation is to create a plain non-java
project to hold the libraries in your workspace. Then you can use Java
Build Path from your web app to reference these jars.
- Konstantin
|
|
|
|
Re: shared lib [message #187777 is a reply to message #187769] |
Thu, 08 February 2007 13:15 |
Eclipse User |
|
|
|
Originally posted by: kosta.bea.com
Basically you want a container to hold jars in the workspace so that you
can refer to them easily from other projects. This way you avoid
absolute paths which don't work in a team environment and you can
source-control this project with the rest of your projects. Since the
project is just a container for jars, it doesn't need to have any
special functionality (such as java compiler) enabled on it. In the
version of Eclipse that I am using, you can create such plain project by
selecting "General -> Project" in the new project wizard.
Hope this helps,
- Konstantin
|
|
|
|
|
|
|
Re: shared lib [message #187817 is a reply to message #187785] |
Thu, 08 February 2007 17:27 |
Eclipse User |
|
|
|
Originally posted by: kosta.bea.com
This shouldn't be a problem for JNI. At runtime you will be using common
instance in the Tomcat's shared lib directory so there is only one
instance. If you put the jars in a shared directory like I suggested,
they will only be used to compile against. The DLLs are not necessary
and will not be loaded.
- Konstantin
|
|
|
Powered by
FUDForum. Page generated in 0.03314 seconds