Hi Ton;
It has done , if you carefully look at the Deployment class loader there is
a meted called getBytes(); it does right thing load the class files in
lib/*.jar , in the mean while I have tested that I am using that feature.
And I know the fact that it does not load the resources in lib/*.jar , I
will try my best to fix that soon , and I am very much thanking for you for
finding this bug (I have not encounter that before).
Thanks,
Deepal
................................................................
~Future is Open~
----- Original Message -----
From: "Tony Dean" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Thursday, December 01, 2005 3:15 AM
Subject: RE: [Axis2] Deployment packaging
I have been doing further testing and have found that the
DeploymentClassLoader is not complete. Resources in lib/*.jar are not found
by the classloader because findResource(name) is not overridden to look for
these resources. Is this being considered? I have classes in /lib/*.jar
that access i18n resource bundles... this does not currently work.
The only way to run successfully is for me to explode the aar so that the
URLClassLoader can load my jars and therefore find my resources.
Any suggestions or comments?
-----Original Message-----
From: Tony Dean
Sent: Tuesday, November 22, 2005 11:07 AM
To: '[email protected]'
Subject: RE: [Axis2] Deployment packaging
Yes, I'd rather not explode, but keep everything compact in aar. I tried it
out and it works nicely. I was confused about where to put lose classes.
Originally, I put them in a "classes/" directory when trying the exploded
way. I repackaged everything in an aar file as follows:
test.aar
meta-inf/services.xml
services.wsdl
com.sas.mySkeleton.class
lib/support1.jar
support2.jar
...
Everything deploys and works cleanly. I was hoping that each service would
have its own classloading hierarchy. Thanks for clearing that up.
Thanks!
-----Original Message-----
From: Sanjiva Weerawarana [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 22, 2005 10:35 AM
To: [email protected]
Cc: [EMAIL PROTECTED]
Subject: RE: [Axis2] Deployment packaging
On Tue, 2005-11-22 at 10:20 -0500, Tony Dean wrote:
Dims,
Just tried it and it appears to work... at least partly.
- I add classes to exploded/classes/ but they were NOT successfully
loaded by the classloader
You need to put the classes in classes/ .. the idea of exploded deployment
is simply to not force you to jar up a directory into a foo.aar file. You
can copy your "foo" directory containing the stuff (including service.xml,
classes/ etc.) to the services/ directory and it should do the right thing.
Sanjiva.
