The current implementation of sessions for rails with jruby uses the java web container session to store the session data. At first blush, this seems like a reasonable thing to do. However, there seem to be issues. In particular, since the session data is kept in memory in the JVM, it never needs to be marshaled/unmarahsled. This seems (though of course, I could be wrong) interact badly with rails trying to reload classes. What I think is see is rails complaining about classes of objects in the session. The classes of those objects has an older object_id from the classes that are reloaded. In a case where the store is serialized, there's always a marshal/unmarshal pass that means the session objects are upgraded to the new class.
Any comments or suggestions? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
