Hi Christian,
I don't like the idea of extensions folder. It makes life easier until
the day you need two versions of a jar. For instance when one
application is not compatiple with version required by another
application.
You can use this instruction for a framework or an application. You can
use the same steps for a framework, just make sure that you export the
jars in 'order and export' tab of the java build path properties page.
Create a folder 'lib' in your project.
Copy the jar(s) into it.
Right click on the project in Eclipse and select refresh.
Again choose from the project context menu the item properties.
Navigate to JavaBuildPath.
Under the 'library' tab click add jar and choose the jar.
Close the properties window.
Open the build.xml file.
Locate the line:
<lib dir=".">
<include name="Add .jar's that should be copied in the woa."/>
<exclude name="**/*.woa/**"/>
</lib>
And change it to:
<lib dir=".">
<include name="lib/*.jar"/>
<exclude name="**/*.woa/**"/>
</lib>
The change in the build.xml makes sure that the lib gets in the woa and
the app classpath. Which means you can deploy the app without coping
any jars. This stuff is also available in the WOLips help. :-)
Am Mittwoch, 30.04.03, um 23:46 Uhr (Europe/Berlin) schrieb Christian
Gruber:
> I have a further question, which may have been answered, but I can’t
> find it. I have used substantial number of files that in production
> are located in
>
> LOCALROOT/Library/Webobjects/Extensions/*.jar (axis, etc.)
>
This archive was generated by hypermail 2.0.0 : Thu May 01 2003 - 16:45:46 EDT