On Tue, 2005-11-22 at 13:38 +0000, Steve Loughran wrote:
>
> I actually create .aar files with no .class in them, just the
> declaration, and make sure the real classes are in the same webapp.
Why do you do that? Is there a particular reason you don't want to
package up the service classes in the .aar?
> > My concern is making other dependent jars available on the classpath
> and doing so without affecting other applications.
>
> remember, each webapp has its own classpath in WEB-INF/lib; anything
> goes in there is private and webapp-wide.
Take a look at
http://marc.theaimsgroup.com/?l=axis-dev&m=113073286309556&w=2
(This has already been fixed and committed.) So we now have a very
flexible class loading model and I'm unclear why you don't want to use
it and want to drop down to putting everything in the webapp class
loader. You *of course* can do that .. but its not as flexible or
powerful as what we now have in Axis2 (think service versioning for
example (for which I have a proposal in progress)).
Sanjiva.
