ActiveVOS 9.x Deployer

[Daniel Luebke]

Hi,

I implemented the first iteration of an ActiveVOS 9.x deployer. Currently, it can deploy and undeploy BPR archives prior/after a test suite is run. However, at the moment it cannot expose the deployment so test coverage reporting and endpoint replacement is not available yet.

I checked with Active Endpoints, Inc. that it is okay for them to have the WSDLs for the administrative services included. Luc Clement from AE agreed as long as the following remark is in the docs (I placed it in markdown documentation found in src/doc):

"Active Endpoints, Inc. is the author of the ActiveVOS commercial product - see www.activevos.com<http://www.activevos.com> for details.
ActiveVOS is a trademark of Active Endpoints, Inc."

I will add the missing features over time although I must admit that the deployment interfacing between BPELUnit and the deployers is really flawed at the moment. In the ActiveVOS deployer you find some of my sketches for a new interface but I am not yet sure how it should look like.

Nevertheless, if you use ActiveVOS please don't hesistate to try out this deployer and provide any feedback.

Daniel

[Antonio García Domínguez]

Hi Daniel,

Thanks for your work! Are there many changes in comparison with the
original ActiveBPEL deployer?

We recently heavily refactored our own BPR builder: it should be much
better now. It's based on WSDL4J, with some extensions of our own.
We'd like to integrate this into BPELUnit someday :-).

Cheers,
Antonio

[Daniel Luebke]

Hi Antonio,

the deployer is not in any way related to the current ActiveBPEL implementation. The administrative services are accessed with JAX-WS (I eliminated the SAAJ dependency because they gave errors due to conflicts with the SAAJ now included in the JDK.)
However, this also means that it currently lacks the interface for modifying the deployment because the code base is completely different. You can have a look at the class - I hope that it's well structured. Perhaps we can rebase the ActiveBPEL deployer to this code? But I don't know whether the services are the same and only the endpoints have changed?

Daniel

[Antonio García Domínguez]

Hi Daniel,

On 25 April 2012 16:29, Daniel Luebke <daniel...@gmail.com> wrote:
> the deployer is not in any way related to the current ActiveBPEL
> implementation. The administrative services are accessed with JAX-WS (I
> eliminated the SAAJ dependency because they gave errors due to conflicts
> with the SAAJ now included in the JDK.)

Oh, I see. Thanks for the catch for SAAJ :-).

> However, this also means that it currently lacks the interface for modifying
> the deployment because the code base is completely different. You can have a
> look at the class - I hope that it's well structured. Perhaps we can rebase
> the ActiveBPEL deployer to this code? But I don't know whether the services
> are the same and only the endpoints have changed?

I'm afraid the WSDL interfaces seem to have changed quite a bit.
Operation names and services are different here and there, and I'm not
even sure if the BPR file format has changed as well :-/. I don't
think we'll be able to reuse much of the old deployment logic. Still,
our BPEL Packager might be useful to produce the BPR files, with
perhaps some adjustments. Have a look here:

https://neptuno.uca.es/redmine/projects/sources-fm/repository/entry/trunk/src/bpel-packager/src/main/java/es/uca/webservices/bpel/activebpel/DeploymentArchivePackager.java

I believe bpel-packager and its dependencies are available as ASL 2.0
libraries, but I'd have to check. Please tell me if you're interested
in reusing the code for BPELUnit.

Antonio

[Daniel Luebke]

Hi Antonio,

it would be a nice component :-) However, I need to see that I fix the functionality like test coverage for the ActiveVOS deployer first...

Daniel