Wapama vs. Oryx

[Tammo van Lessen]

Hi guys,

I was wondering about the differences between Wapama and Oryx. What are the most significant changes? Why has it been forked? What can Wapama do that Oryx cannot (or vice versa)? Would be great if someone could shed some light on this. Also, the latest commit was 6 months ago, is it still maintained and will it be continued in future?

Thanks,
  Tammo

[Antoine Toulme]

Wapama is much lighter than Oryx. It is consolidated and streamlines the backend to ensure it can be used with other services, for example a JSR repository like Drools started with. The metamodel can also be served programmatically - an improvement over the Oryx metamodels that were static json files.

Oryx tries to support a number of plugins. They were removed in Wapama - for example, the BPEL plugins - as they were not good enough or not tested well, or just didn't cut it.

There is also the community aspect. Wapama was meant to be an open source project with proper releases.

The project is not actively maintained anymore, but in the tradition of github, there are several forks out there that have much more activity. You should investigate and see what is going on.

Wapama like Oryx still has a dependency over extJS v2.0.2. You might also want to investigate the legal implications of using the software with that dependency, or spend the time necessary to get rid of it for something like jQuery.

I hope that helps!

Antoine

[Zhenshan Wen]

I'm also wondering the relationship between Wapama and Oryx. I'm only interested in the Javascript based client UI and these two looks very very similar. From the license of Wapama, I don't see any statement that Wapama is based on Oryx's codes. But I see most of the javascript codes are almost same including the declared authors. Is Wapama just a simplified modification of Oryx?

Thanks,

Zhenshan

[Oliver]

Hi,

> I'm only interested in the Javascript based client UI and these two looks very very
> similar.

From Oryx, the signavio core components have been forked. They contain
only the UI part:
http://code.google.com/p/signavio-core-components/

A github mirror is available at:
https://github.com/IAAS/signavio-core-components/

Cheers,

Oliver

[Antoine Toulme]

Zhenshan,

Wapama is based off Oryx, of course. It is indeed a largely simplified version of Oryx, with a ton of cleanup work to make it more stable.

It still has a dependency to Extjs that you need to be aware of. Otherwise it works pretty well.

Antoine

[Zhenshan Wen]

Thanks, Antonie.

Is the Extjs that wapama uses ever modified? I want to know if there is any license issue if I want to use wapama in a commercial product.

[Zhenshan Wen]

Yea, I also noticed that. Looks like both signaviocore and wapama are based on Oryx.

[Antoine Toulme]

It was not.

[Tihomir Surdilovic]

IIRC the Ext licence changes (dual licensing) took affect in 2.1. Wapama should be using 2.0.2, so you should be OK, but don't quote me on that :)

Thanks.

[Antoine Toulme]

Yes, typically no lawyers subscribed to this mailing list.