Pid-2 wrote:
>
>
> Actually, I disagree. I have deployed the Axis and support jars in a
> shared classloader (shared/lib for TC5.5) and then deployed a .war for
> each webapp.
>
> In your case you could do:
>
> /app1/axis/services/
> /app2/axis/services/
>
> You're both correct. Th
JavierL wrote:
Rashmi Rubdi-2 wrote:
Javier,
I don't know much about Webservices and Axis in particular, but at one
time I did download the Axis distribution.
In the lib folder of the Axis distribution there are a few JAR files
axis.jar, wsdl4j-1.5.1.jar etc.
Normally, when I write multiple
Rashmi Rubdi-2 wrote:
>
> Javier,
>
> I don't know much about Webservices and Axis in particular, but at one
> time I did download the Axis distribution.
>
> In the lib folder of the Axis distribution there are a few JAR files
> axis.jar, wsdl4j-1.5.1.jar etc.
>
> Normally, when I write multi
Javier,
I don't know much about Webservices and Axis in particular, but at one
time I did download the Axis distribution.
In the lib folder of the Axis distribution there are a few JAR files
axis.jar, wsdl4j-1.5.1.jar etc.
Normally, when I write multiple projects that use JAR files from
differe
Rashmi Rubdi-2 wrote:
>
>
> From my experience, adding Jars for different apps in the same lib
> folder will cause conflicts and duplicates, especially if one person
> is using a JAR for one version and another is using a different
> version.
>
> However, you can have different projects with e
On 4/25/07, JavierL <[EMAIL PROTECTED]> wrote:
Hi
I've a an Axis war where a lot of people publish applications and then, lib
directory is caotic with a lot of jar files. Each time somebody delete your
webservice application, he/she can't delete related jar files because
ignores if somebody el
