Thanks for the reply. Doesn't it give you guys the willys to have to alter a support archive (axis2.war)? My company frowns upon opening up jars in the application server and altering that code, as I'm sure you understand. Bea/JBoss/Eracle do not support AS code they didn't write, why is it okay to do this for axis? I wouldn't open up spring-orm.jar to add my own code, why should I be expected to do this with axis2.war? This kinda smells.

On 12/15/05, Srinath Perera < [EMAIL PROTECTED]> wrote:
> put the shared objects in a jar in the axis2/WEB-INF/lib folder
> I think it works
Yes it does ..:)

regarding putting services inside the war file ..may be we need to add
a support to have repository in file system (e.g. your home
directory/.axis2).

Thanks
Srinath

On 12/15/05, Manuel Salvadores <[EMAIL PROTECTED]> wrote:
> On 12/14/05, Todd Orr <[EMAIL PROTECTED] > wrote:
> > Also, how would you version the services now? I used to be able to create a
> > separate war with a different url-pattern based on version. Now that
> > services are deployed under one war, how can I differentiate?
> >
> >
> >  On 12/14/05, Todd Orr <[EMAIL PROTECTED]> wrote:
> > > Also, how do you share global objects now? I used to be able to create an
> > entire war and share any objects I needed to. Now that the services are in
> > individual aar files, where do I put the shared objects?
> > >
> > >
> > >
> > > On 12/14/05, Todd Orr < [EMAIL PROTECTED]> wrote:
> > > > The changes in the deployment options from Axis1 to Axis2 are very
> > disruptive. The web admin for uploading new services is nice for testing,
> > but makes my company's deployment scripts useless. The fact that the aar
> > files need to be placed in the exploded axis2 war's services directory makes
> > deployment a real pain. Axis1 was very simple and easy to use since it was
> > only a regular webapp. I've been reading through the docs, and I do not see
> > any other deployment options. Has anyone found any better ways to deploy
> > axis2 services?
> > > >
> > >
> > >
> >
> >
>

Reply via email to