Deserialization problems with process variables - continuing about activiti-spring-security HOT 3 OPEN

You are right. :)

Thanks for report this issue.

from activiti-spring-security.

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.

from activiti-spring-security.

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

from activiti-spring-security.