Well for the client side you can just drop the modules into the class path and engage them at the runtime. In that case you do not need to worry about creating a configuration context.
Thank you! Deepal > Many thanks, I didn't spot that particular flavour of > method createConfigurationContext > > Paul > > ------------------------------------------------------------------------ > *From:* Eran Chinthaka [mailto:eran.chinth...@gmail.com] > *Sent:* 29 December 2008 16:42 > *To:* axis-user@ws.apache.org > *Subject:* Re: client side modules > > ConfigurationContext configContext = > ConfigurationContextFactory.createConfigurationContextFromFileSystem( > > null, pathToYourRepository); > > SimpleHTTPServer simpleServer = new SimpleHTTPServer(configContext, > <YourPort>); > > simpleServer.start(); > > > > With Mettha, > Eran Chinthaka > > -------------------------------------------------------------------- > Health is the greatest gift; contentment is the greatest wealth; > trusting is the best relationship; nirvana is the highest joy. - > Dhammapada > > > On Mon, Dec 29, 2008 at 11:14 AM, Paul French <paul.fre...@kirona.com > <mailto:paul.fre...@kirona.com>> wrote: > > Can anyone give me any pointers how to deploy a module on the > client side? > > If I create a client stub to call a web service from within a web > application that also provides an axis2 web service then I believe > all I need to do is re-use the configuration context created by > the web service? Is this correct? > > What about in a standalone java application. How do I deploy a > module in that scenario. Since I do not have a web application I > don't have a WEB-INF/modules/ file structure? > > I'm a bit lost, any help will be appreciated. > > Thanks > Paul > > > > -- Thank you! http://blogs.deepal.org http://deepal.org
