On Jan 26, 6:02 pm, "aptosca" <[EMAIL PROTECTED]> wrote: > The current implementation of sessions for rails withjrubyuses 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.
I assume you're using the "rails integration" module that allows you to run a Rails app as a WAR file. It seems odd that there would be a problem storing the Rails session in the Java app server session, since Rails itself provides an in-memory store to use in the same way. If you can narrow down what's actually the problem, maybe we can figure out how to resolve it. The other option would be to see if it continues to happen in production mode, where classes aren't mutated and reloaded as much (or at all?). - Charlie --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
