Hi,
When you engage the module to client it has to be engaged each time you
instantiate a new ServiceClient. Each time the module is engaged it will
be extracted into the temp folder to do class loading much faster.
You can avoid this by engaging the module to the
ConfigurationContext[1]. Then it will be done only once.
Thank you,
Dimuthu
[1]
ConfigurationContext ctx =
ConfigurationContextFactory.createConfigurationContextFromFileSystem(path, path
+ "/conf/axis2.xml");
ctx.getAxisConfiguration().engageModule("rampart");
On Thu, 2008-04-03 at 15:59 -0700, A Sunley wrote:
> Greetings Axis users,
>
> We are accessing a web service from within a jsp/servlet webapp within a
> Tomcat container, using Axis2-1.2. We also make use of the Rampart security
> module.
>
> I want to clarify how we should 'engage' module. At the moment we do this
> for every request to the webservice using:
>
> client.engageModule(new QName("rampart"));
>
> Do we have to do this for each and every request or can we delpoy the module
> once for the web application?
>
> I am noticing that for each request the following is printed to the console:
> "Deploying module: rampart-1.2". In addition the Tomcat/temp folder is
> chocker full of "axis264rampart-1.2.mar" files (each with a different
> number). The temp file is now approaching one gigabyte in size.
>
> Is this normal behavior? I'm concerned that I might have not configured the
> Axis2 client correctly and may potentially cause performance issues.
>
> Is this that case?
>
> Regards,
> Alan.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
