Deployment Architecture

[Daniel Luebke]

Hi,

I started to design a new deployer/deployment architecture. The goal is to have an IDeployment interface which can be used by mocking, test coverage instrumentation, ... for accessing and changing the deployment in an engine-independent manner.

The interface is still only in the ActiveVOS 9.x deployer project so that it does not conflict with the other deployers and keeps the framework buildable.

The main idea is to have the deployer interface deliver an IDeployment to the other framework parts. The IDeployment can deliver BPELProcesses which are identified by their QNames. The XML can be changed by all components and shall be written back to the deployment transparently when deploying. For changing things that will also impact the deployment descriptors or the archive contents additional methods are offered (adding WSDLs, changing endpoints, ...)

Any remarks, suggestions or critiques?

Daniel

[Daniel Luebke]

Hi,

building upon the deployment I have implemented the mocking for waits (i.e. changing to a defined small duration so that tests can complete within a reasonable time.) This is also the start to add components to the test cycle. Here before deploying. There would also be a component for changing endpoints and a component for test coverage measurement. Porting these to the new architecture will add new features to the IDeploymentChanger interface.

Everything is still in the ActiveVOS deployer project... Next step for me would be to move the ODE Deployer to the new interface and move the new interfaces into the main framework project. We have ActiveBPEL available for testing the changes to its deployer, however, I lack the old oracle version for which the Oracle deployer is there. It's so old that perhaps we drop it? I don't know...

Daniel

[Daniel Luebke]

Just a short update: WaitMock is now called TimeMock and can also change onAlarms in <pick>s and event handlers.

[Antonio García Domínguez]

Hi Daniel,

Sorry about this short message, but I have my hands full with other
things now :-(.

On 12 May 2012 15:43, Daniel Luebke <daniel...@gmail.com> wrote:
> building upon the deployment I have implemented the mocking for waits (i.e.
> changing to a defined small duration so that tests can complete within a
> reasonable time.) This is also the start to add components to the test
> cycle. Here before deploying. There would also be a component for changing
> endpoints and a component for test coverage measurement. Porting these to
> the new architecture will add new features to the IDeploymentChanger
> interface.

Sounds nice :-). Perhaps we could rebase the code coverage bits on top
of this new design and add some tests while we're at it, don't you
think?

> Everything is still in the ActiveVOS deployer project... Next step for me
> would be to move the ODE Deployer to the new interface and move the new
> interfaces into the main framework project. We have ActiveBPEL available for
> testing the changes to its deployer, however, I lack the old oracle version
> for which the Oracle deployer is there. It's so old that perhaps we drop it?
> I don't know...

I suggest that we drop support for it. I don't think it will have many
active users by now, and they could simply stay with BPELUnit 1.6.0.

Best regards,
Antonio