Yes, that is what I have reverted to doing. I have an issue with my business logic such that it will only work correctly when some of the bundled resources are held as real files on Tomcat, rather than contained in a Jar.
I really should fix this problem, but I was hoping for a quick fix that would allow me to deploy an aar file and then let Axis2 unpack it into the typical directory tree layout. It's easier to manage the single aar file in my build system. Thanks anyway. -----Original Message----- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: 31 May 2007 13:47 To: [email protected] Subject: Re: Forcing the unpacking of aar files Des, You can actually deploy an unpacked aar : http://www.developer.com/open/article.php/10930_3557741_2 -- dims On 5/31/07, Desmond Whewell (CV/ETL) <[EMAIL PROTECTED]> wrote: > > Is there a configuration option that will force Axis2 (1.2) to unpack > the the aar files upon deployment? > > Cheers, Des > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Davanum Srinivas :: http://davanum.wordpress.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
