Deserialization problems with process variables - continuing #4

Open
acoulson2000 opened this Issue Dec 19, 2012 · 3 comments

Projects

None yet

2 participants

@acoulson2000

The class deserialization issue described here:

limcheekin/activiti#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
Owner

You are right. :)

Thanks for report this issue.

@acoulson2000

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
Owner

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment