integration Blaze Rules application

Hi,

I would actually urge you to keep integration out of your rule service. Embedding for example data lookup and persistence in your rule service makes the service harder to test, and it also makes it harder to tune your rules.

You should also consider the fact that BA is not a transactional resource, which means that you are solely responsible for making reads (at the start of the service invocation) and writes (at the end) part of the same transaction. Obviously not impossible, but why fight the technology?

Pass all the data you need into your rule service, and return any and all results. That way you are more easily integrated into other solutions. In your first version you can handle data lookup/persistence in the Java web service wrapper that you create. That way it will be part of your service, but not your rule service.

Regards,

Jostein