David Kerber wrote:
Mikolaj Rydzewski wrote:
I'd deploy this library as a separate application (even on the same
Tomcat) and access its interface by RMI, WS, or something like that.
Wouldn't I need to rewrite my command-line and jni apps to do this?
Probably ;-)
I don't know what your lib
Mikolaj Rydzewski wrote:
David Kerber wrote:
I have a library (.jar file) that is used with 3 different apps:
with my tomcat webapp, with a standalone command-line app, and with a
jni package that provides a .dll for use with a windows gui app.
What is the best way (place) to deploy this j
Put it in the proper place for each app. IMHO a few copies is better
than attempting to put it in only one place and then dealing with
compatibility issues as the library is updated.
--David
David Kerber wrote:
> No one has a suggestion about this?
>
>
> David Kerber wrote:
>
>> This is on Windo
David Kerber wrote:
I have a library (.jar file) that is used with 3 different apps: with
my tomcat webapp, with a standalone command-line app, and with a jni
package that provides a .dll for use with a windows gui app.
What is the best way (place) to deploy this jar? It appears that
puttin
No one has a suggestion about this?
David Kerber wrote:
This is on Windows server 2003.
I have a library (.jar file) that is used with 3 different apps: with
my tomcat webapp, with a standalone command-line app, and with a jni
package that provides a .dll for use with a windows gui app.
This is on Windows server 2003.
I have a library (.jar file) that is used with 3 different apps: with
my tomcat webapp, with a standalone command-line app, and with a jni
package that provides a .dll for use with a windows gui app.
What is the best way (place) to deploy this jar? It appears
