So embedding a service is the only solution here? There is no easy way to tell axis2 where your libraries or dependent classes are other than place them directly under the axis2 tree?
-----Original Message----- From: dimension123 [mailto:[email protected]] Sent: Saturday, March 28, 2009 2:26 AM To: '[email protected]' Subject: RE: Axis2 webservice - access to existing application classes outside of axis service/repository tree My "webservice's source here..", I mean either the compiled classes and all dependencies. The webservice implementation classes I have no problem with, but this service relies on libraries and classes, as well as exposes pojos from an application that already exists and in production. That app runs under the same instance of tomcat as axis2. I was hoping it would be as simple as being able to set a classpath. -----Original Message----- From: Sagara Gunathunga [mailto:[email protected]] Sent: Saturday, March 28, 2009 1:15 AM To: [email protected] Subject: Re: Axis2 webservice - access to existing application classes outside of axis service/repository tree Hi , > It appears that axis2 requires you to place your webservice's source in > addition to ALL libraries or classes that that service interacts with under > > webapps/axis2/WEB-INF/services. What do you mean "webservice's source here ...? > Or is there a way to configure axis so that we do not have to deploy under > the axis2/ tree, but instead tell it where the class files that will act as > the service is located in the existing app? It seems you already running your application as a .WAR format , you can integrate Axis2 under your existing application by editing web.xml and placing required meta data files, not required to bring your existing application under the axis2/ tree. please refer [1] [1] - http://www.developer.com/open/article.php/3777111 Thanks , -- Sagara Gunathunga Blog - http://ssagara.blogspot.com Web - http://sagaras.awardspace.com/
