You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Glenn Williams <gl...@iosemantics.com> on 2007/09/04 16:16:39 UTC
Runtime best practices for Axis2
What are the best practices for passing runtime parameters (such as DB
login, pooling parameters) to the Axis2 container?
RE: Runtime best practices for Axis2
Posted by Glenn Williams <gl...@iosemantics.com>.
Sanka wrote:
" IMHO, configuration file of a service should be included in service.aar
file.
I would put it inside META-INF folder inside service.aar and later read it
via service class loader."
That means for any configuration change such as runtime pooling the user has
to redeploy the .aar file? This isn't acceptable in a production system that
needs to load balance or change dynamic values such as database location or
login, in real time, and by sys admins who do not develop the software.
Apache configuration tools provide means in real time to pick up
configuration changes for example, but there seems to be no way to use this
feature in an Axis2 web service.
The only way I see is to expand the runtime code into the service directory
and get rid of the .aar file.
Anybody see any other option?
-----Original Message-----
From: Sanka Samaranayke [mailto:ssanka@gmail.com]
Sent: Sunday, September 09, 2007 9:59 PM
To: axis-user@ws.apache.org
Subject: Re: Runtime best practices for Axis2
Glenn Williams wrote:
> Axis2.xml, from the documentation, is supposed to be for global
> configuration. But it is available outside .AAR file so a user could
change
> the configuration without repackaging the .AAR file. But that seems to
> violate the usage of the axis2.xml file. Any thoughts?
>
> What do you think about putting a configuration file for the given service
> in the Axis2 conf directory? Is that directory available to the service at
> runtime?
>
IFAIK, you only get access to ConfigurationContext which reflects
configuration
specified in axis2.xml in runtime. You can't access the contents of axis2
conf
directory directly.
IMHO, configuration file of a service should be included in service.aar
file.
I would put it inside META-INF folder inside service.aar and later read it
via service class loader.
Thanks,
Sanka
> -----Original Message-----
> From: Deepal jayasinghe [mailto:deepalk@gmail.com]
> Sent: Thursday, September 06, 2007 4:54 AM
> To: axis-user@ws.apache.org
> Subject: Re: Runtime best practices for Axis2
>
> Glenn Williams wrote:
>
>> What are the best practices for passing runtime parameters (such as DB
>> login, pooling parameters) to the Axis2 container?
>>
>>
>>
>>
>>
>>
> You can add them as parameters in axis2.xml or you can have a module to
> initialize them and add those to container. In the case of module
> approach you have to write a module with a Module class and inside the
> module init method you need to do the processing.
>
> Thanks
> Deepal
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
>
--
Sanka Samaranayake
WSO2 Inc.
http://www.bloglines.com/blog/sanka
http://www.wso2.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Runtime best practices for Axis2
Posted by Sanka Samaranayke <ss...@gmail.com>.
Glenn Williams wrote:
> Axis2.xml, from the documentation, is supposed to be for global
> configuration. But it is available outside .AAR file so a user could change
> the configuration without repackaging the .AAR file. But that seems to
> violate the usage of the axis2.xml file. Any thoughts?
>
> What do you think about putting a configuration file for the given service
> in the Axis2 conf directory? Is that directory available to the service at
> runtime?
>
IFAIK, you only get access to ConfigurationContext which reflects configuration
specified in axis2.xml in runtime. You can't access the contents of axis2 conf
directory directly.
IMHO, configuration file of a service should be included in service.aar file.
I would put it inside META-INF folder inside service.aar and later read it
via service class loader.
Thanks,
Sanka
> -----Original Message-----
> From: Deepal jayasinghe [mailto:deepalk@gmail.com]
> Sent: Thursday, September 06, 2007 4:54 AM
> To: axis-user@ws.apache.org
> Subject: Re: Runtime best practices for Axis2
>
> Glenn Williams wrote:
>
>> What are the best practices for passing runtime parameters (such as DB
>> login, pooling parameters) to the Axis2 container?
>>
>>
>>
>>
>>
>>
> You can add them as parameters in axis2.xml or you can have a module to
> initialize them and add those to container. In the case of module
> approach you have to write a module with a Module class and inside the
> module init method you need to do the processing.
>
> Thanks
> Deepal
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
>
--
Sanka Samaranayake
WSO2 Inc.
http://www.bloglines.com/blog/sanka
http://www.wso2.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
RE: Runtime best practices for Axis2
Posted by Glenn Williams <gl...@iosemantics.com>.
Axis2.xml, from the documentation, is supposed to be for global
configuration. But it is available outside .AAR file so a user could change
the configuration without repackaging the .AAR file. But that seems to
violate the usage of the axis2.xml file. Any thoughts?
What do you think about putting a configuration file for the given service
in the Axis2 conf directory? Is that directory available to the service at
runtime?
-----Original Message-----
From: Deepal jayasinghe [mailto:deepalk@gmail.com]
Sent: Thursday, September 06, 2007 4:54 AM
To: axis-user@ws.apache.org
Subject: Re: Runtime best practices for Axis2
Glenn Williams wrote:
>
> What are the best practices for passing runtime parameters (such as DB
> login, pooling parameters) to the Axis2 container?
>
>
>
>
>
You can add them as parameters in axis2.xml or you can have a module to
initialize them and add those to container. In the case of module
approach you have to write a module with a Module class and inside the
module init method you need to do the processing.
Thanks
Deepal
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Runtime best practices for Axis2
Posted by Deepal jayasinghe <de...@gmail.com>.
Glenn Williams wrote:
>
> What are the best practices for passing runtime parameters (such as DB
> login, pooling parameters) to the Axis2 container?
>
>
>
>
>
You can add them as parameters in axis2.xml or you can have a module to
initialize them and add those to container. In the case of module
approach you have to write a module with a Module class and inside the
module init method you need to do the processing.
Thanks
Deepal
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org