search

limcheekin / activiti-spring-security

Activiti Spring Security Integration
Apache License 2.0
7 stars 16 forks source link

Deserialization problems with process variables - continuing #4

Open acoulson2000 opened 11 years ago

acoulson2000 commented 11 years ago

The class deserialization issue described here:

https://github.com/limcheekin/activiti/pull/1

seems to still exist when using activiti-spring-security, presumably because this plugin is not intializing the processEngineConfiguration with the new custom variable type:

            processEngineConfiguration(org.activiti.spring.SpringProcessEngineConfiguration) {
                            ...
                customPreVariableTypes = [new SerializableVariableType()]
                            ...

Recommend adding this injection in ActivitiSpringSecurityGrailsPlugin too.

limcheekin commented 11 years ago

You are right. :)

Thanks for report this issue.

acoulson2000 commented 11 years ago

What do you think about this issue:

https://groups.google.com/forum/?fromgroups=#!searchin/grails-activiti-plugin/deserialization/grails-activiti-plugin/mD0aJKhiZE4/DjYWSPvUl7QJ

I didn't report it as in issue on github because the code works without it, I thinks it's more of an inconvenience and slight inefficiency in terms of how primitives are stored in the database. I suspect it would also be a problem if you do anything with process variables created in grails, but then viewed outside of a grails context - in the Activiti Explorer, for instance.

limcheekin commented 11 years ago

Thanks for writing and sharing. I couldn't comment at the moment as I didn't spent enough effort investigate it.