Hello,
I'm trying to achieve the same thing.
I'm using activiti 5.4.
My approach was to add a CustomIdentitySessionFactory to the SpringProcessEngineConfiguration
<bean id="processEngineConfiguration" class="org.activiti.spring.SpringProcessEngineConfiguration">
<property name="dataSource" ref="dataSource" />
<property name="transactionManager" ref="transactionManager" />
<property name="databaseSchemaUpdate" value="true" />
<property name="jobExecutorActivate" value="false" />
<property name="dbCycleUsed" value="true" />
<property name="customSessionFactories">
<list>
<bean class="de.hlux.activiti.custom.spring.CustomIdentitySessionFactory"></bean>
</list>
</property>
</bean>
public class CustomIdentitySessionFactory implements SessionFactory {
public Session openSession() {
return (Session) new CustomIdentitySession();
}
public Class<?> getSessionType() {
return IdentitySession.class;
}
}
This works so far.
The thing I'd like some help with is to find the best way to inject the second datasource.
ProcessConfigurationImpl uses the following code to create a SqlSessionFactory
protected void initSqlSessionFactory() {
if (sqlSessionFactory==null) {
InputStream inputStream = null;
try {
inputStream = ReflectUtil.getResourceAsStream("org/activiti/db/ibatis/activiti.ibatis.mem.conf.xml");
// update the jdbc parameters to the configured ones…
Environment environment = new Environment("default", transactionFactory, dataSource);
Reader reader = new InputStreamReader(inputStream);
XMLConfigBuilder parser = new XMLConfigBuilder(reader);
Configuration configuration = parser.getConfiguration();
configuration.setEnvironment(environment);
configuration.getTypeHandlerRegistry().register(VariableType.class, JdbcType.VARCHAR, new IbatisVariableTypeHandler());
configuration = parser.parse();
sqlSessionFactory = new DefaultSqlSessionFactory(configuration);
} catch (Exception e) {
throw new ActivitiException("Error while building ibatis SqlSessionFactory: " + e.getMessage(), e);
} finally {
IoUtil.closeSilently(inputStream);
}
}
}
That is used within the DbSqlSessionFactory
dbSqlSessionFactory = new DbSqlSessionFactory();
dbSqlSessionFactory.setDatabaseType(databaseType);
dbSqlSessionFactory.setIdGenerator(idGenerator);
dbSqlSessionFactory.setSqlSessionFactory(sqlSessionFactory);
dbSqlSessionFactory.setDbIdentityUsed(isDbIdentityUsed);
dbSqlSessionFactory.setDbHistoryUsed(isDbHistoryUsed);
dbSqlSessionFactory.setDbCycleUsed(isDbCycleUsed);
addSessionFactory(dbSqlSessionFactory);
At the moment I think, that my CustomIdentitySession should make use of a DbSqlSessionFactory,
but that of course needs to have the datasource where the users and groups are stored.
I'm not familiar enough with the design patterns used and would like to hear you opinion on my approach.
Maybe I'm completely wrong here.
greetings
hlux
