The class deserialization issue described here:
seems to still exist when using activiti-spring-security, presumably because this plugin is not intializing the processEngineConfiguration with the new custom variable type:
customPreVariableTypes = [new SerializableVariableType()]
Recommend adding this injection in ActivitiSpringSecurityGrailsPlugin too.
You are right. :)
Thanks for report this issue.
What do you think about this issue:
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.
Thanks for writing and sharing. I couldn't comment at the moment as I didn't spent enough effort investigate it.