axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ruchith Fernando" <>
Subject Re: [AXIS2] OutflowSecurity configuration
Date Thu, 10 Aug 2006 02:16:59 GMT
Hi aj,

Yes its possible to set the configuration dynamically within the
service (for the service client).

If you are using the nightly build then you can use
org.apache.rampart.handler.config.OutflowConfiguration and
org.apache.rampart.handler.config.InflowConfiguration for this. You
can create instances of the above classes and set different config
parameters using the available setter methods (See [1]
getOutflowConfiguration() and getInflowConfiguration()). Then you can
obtain an Axis2 parameter form each of the above instances by calling
getProerty(). This parameter instance can be set in the options object
of the ServiceClient (See here [2] invokeWithGivenConfig()).


On 8/10/06, Jones, Alan R <> wrote:
> Assuming there are several services deployed to the same axis2
> deployment (Tomcat) and they all need to talk to each other with secured
> messages...
> Each service is also a client of one or more other services. Therefore,
> each service will need its own axis2.xml in order to config its keystore
> alias/user, the, etc. via OutflowSecurity entry. This
> implies a separate axis2 "client" repository for each provider/consumer,
> which in turn requires a certain directory structure (repos/conf,
> repos/modules, etc) since axis throws errors when the structure is
> absent. This is not desirable. Soooo...
> Is it possible to instead dynamically set the OutflowSecurity parameters
> inside each service, as it begins to make its call to an external
> service, eliminating the need for a static config file and all its
> attendant other stuff?
> Thanks,
> aj
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message