Activiti version numbering

briantopping — Sun, 19 Sep 2010 18:20:30 GMT

As I started integrating Activiti to my project, I was happy to find the IdentityService interface and easily integrated a stubbed implementation via Spring, with breakpoints to dynamically view usages. So far, so good. After running my test framework, I was surprised to find that none of the meth

Re: Activiti version numbering

tombaeyens — Mon, 20 Sep 2010 06:32:20 GMT

IdentityService is our identity API. Should be used in our test suite.
IdentitySession is our identity SPI. That is the interface for which we would very much like to have a Spring Security binding.

Since we are pressed in time, we focus on API first. That should be stable. SPI's are not yet considered stable. Good point that we should document that better.

Some background that might help understand Activiti identity approach: Internally in our own runtime engine persistence, we only store userId references as String's. That is exactly to enable easy pluggability of the IdentitySession. Not all bindings will have all the features that might be exposed in the full IdentitySession. So our impl uses the IdentitySession for very specific functions and as minimal as possible. This makes it easy to start implementing a basic binding with e.g. Spring Security. You can use most of Activiti by just implementing the basic IdentitySession methods. Only for the specific features, other method implementations will be used.

You should start plugging the IdentitySession by building a ProcessEngineConfiguration programmatically. Then supply a different implementation for the IdentitySessionFactory in the sessionFactories property. Keep us posted.

topic Activiti version numbering in Alfresco Archive

Activiti version numbering

Re: Activiti version numbering