https://bitbucket.org/idempiere/idempiere/commits/37c82df
https://bitbucket.org/idempiere/idempiere/commits/568e8f5

https://bitbucket.org/idempiere/idempiere/commits/c950b1c
https://bitbucket.org/idempiere/idempiere/commits/dbe76a0

https://bitbucket.org/idempiere/idempiere/changeset/4879774ccb0cacd7f2c8d99d7b325b7fc0b17d1a
https://bitbucket.org/idempiere/idempiere/changeset/9e9b67b98f59b554de156829a8d7b81c0ca46bef

http://wiki.idempiere.org/en/NF001_Fitnesse_Integration

Note: The SLIM support code is there but only Fit fixture have been tested.

Bringing some mail conversations about this topic:

___________

Carlos Ruiz wrote:
Hi Heng Sin, David is exploring the integration of fitnesse with OSGi, and of course we found the first stopper when trying to execute it directly with the usual JVM used for fitnesse+adempiere.

Googling we found a couple of links that David is starting to study:
http://www.microdoc.com/efitnesse
http://lsd.luminis.nl/fitnesse-and-osgi/

___________

Heng Sin wrote:
eFitnesse looks like is probably the good way to go. There's a difference from the article compare to our environment where we support the deployment of an OSGi war bundle. Instead of using equinox http service, we can make the fitness server a normal osgi war bundle ( like zk and webstore ) and install that just as any other bundle and it will be started as part of the idempiere server. this approach can be used with the standard fitness server, i.e we can package a custom fitness server as an osgi war bundle and install it as part of the adempiere server.

___________

Heng Sin wrote:

Hi Carlos,
I've download and take a look at the code from http://lsd.luminis.nl/fitnesse-and-osgi/ . It uses remote http call and you just need a to add a fixtureservlet to idempiere to expose the fixture available. It needed very few if any modification to fitness but added the maintenace burden of a new remote protocol.

___________