Is there any way I can share classes between two or more war files?.
in app2.war I have a servlet that makes a call to Package1Class that is in app1.war.
How can I do this?. I see that I can define a list of packages as systemClasses. I tried and it doesn't seem to work, maybe a miss configure something.
I prefer not to put all my common classes in a jar that will live in $JETTY_HOME/lib to be loaded at startup if is possible.
$JETTY_HOME/lib to be loaded at startup if is possible.
access those classes from a common classloader.
into a jar in $jetty.home/lib/ext.
jetty.class.path to specify extra common classpaths on the runline.
> Is there any way I can share classes between two or more war files?.
> Is this the way to do it?
> $JETTY_HOME/lib to be loaded at startup if is possible.
Thank you for your response, it's pretty much what I thought.
research on jetty mailing lists.
I completely misunderstood it's meaning).
customer folder that is in jetty.class.path).
classloader instead of the default (see WebAppContext.setClassLoader(ClassLoader)).
> Thank you for your response, it's pretty much what I thought.
> research on jetty mailing lists.
> I completely misunderstood it's meaning).
> customer folder that is in jetty.class.path).
> access those classes from a common classloader.
> into a jar in $jetty.home/lib/ext.
> jetty.class.path to specify extra common classpaths on the runline.
>> Is there any way I can share classes between two or more war files?.
>> Is this the way to do it?
>> $JETTY_HOME/lib to be loaded at startup if is possible.
>> Still grepping through log files to find problems? Stop.
Though its been years since it was answered, I just want to confirm this..
I have two webApps say war1 and war 2. These two war files shares common functionalities. Hence, I packed these functionalities into a JAR file and access it using manifest file. Is this can be used or should I prefer custom class loader?