mixed deployment

[Henrik Vendelbo <hv...@bluprints.com>]

I am working on a deployment setup that is a mixture of WSDD deployment and
database driven.

Essentially I want to deploy according to a WSDD in the usual way and then
add extra services
based on a database of virtual host accounts.

1) Walked through the Axis System Integration Guide and set up a new
EngineConfigurationFactory using META-INF etc - DONE, excellent guide !
2) I then made a MixedProvider that is constructed on FileProvider, and just
calls through - DONE
3) Next up I wrap a MixedProvider around the FileProvider in
getServerEngineConfig() - DONE
4) Now I need to extend the functionality in
MixedProvider.configureEngine(AxisEngine engine) - HOW ?

I could call fileProvider.configureEngine, then another configureEngine, and
finish with engine.refreshGlobalOptions()
Yet I wonder if the refresh function is built to be called multiple times

Or should I create an inside-out Engine wrapper and inject the extra
configureEngine call in the call of wrapper configureEngine ?

Any suggestions on which approach to go for ?

Henrik

Re: mixed deployment

[Henrik Vendelbo <hv...@bluprints.com>]

I just revisited SimpleProvider and noticed the default configuration
parameter on the constructor.

It basicly provides what I am looking for. Even so it seems only half way
finished, can anyone verify this?

Viewing the services for instance doesnt show my WSDD services although they
still work. Looking at
the class implementation, it seems that there is no chaining to the default
configuration once something is
configured for simple.

Am I correct ?

----- Original Message ----- 
From: "Henrik Vendelbo" <hv...@bluprints.com>
To: <ax...@ws.apache.org>
Sent: Friday, October 17, 2003 1:03 AM
Subject: mixed deployment


> I am working on a deployment setup that is a mixture of WSDD deployment
and
> database driven.
>
> Essentially I want to deploy according to a WSDD in the usual way and then
> add extra services
> based on a database of virtual host accounts.
>
> 1) Walked through the Axis System Integration Guide and set up a new
> EngineConfigurationFactory using META-INF etc - DONE, excellent guide !
> 2) I then made a MixedProvider that is constructed on FileProvider, and
just
> calls through - DONE
> 3) Next up I wrap a MixedProvider around the FileProvider in
> getServerEngineConfig() - DONE
> 4) Now I need to extend the functionality in
> MixedProvider.configureEngine(AxisEngine engine) - HOW ?
>
> I could call fileProvider.configureEngine, then another configureEngine,
and
> finish with engine.refreshGlobalOptions()
> Yet I wonder if the refresh function is built to be called multiple times
>
> Or should I create an inside-out Engine wrapper and inject the extra
> configureEngine call in the call of wrapper configureEngine ?
>
> Any suggestions on which approach to go for ?
>
> Henrik
>
>
>
>
>
>