The requirement that Session objects and objects attached it should be
Serializable is not new. It has been there right from the beginning of
OpenCMIS but wasn't implemented properly.
We want to make sure that you can put a Session object into a
HttpSession. That allows Servlet engines to swap out HttpSessions to
disk or transfer sessions to other cluster nodes.
- Florian
On 22/11/2010 13:18, Florent Guillaume wrote:
Another question:
Why the new requirement that Session, CmisObject& co be Serializable?
In my local bindings, sessions and objects are created from
non-Serializable objects from the underlying repository API, and I
cannot easily make them truly Serializable. I have underlying
connection-like objects that come from a transactional context which
are definitely not Serializable.
What do you think?
Florent
On Wed, Nov 17, 2010 at 11:01 AM, Florian Müller
<[email protected]> wrote:
Hi all,
Merge is done. Please test and provide feedback.
Thanks,
Florian
On 15/11/2010 13:50, Florian Müller wrote:
Hi all,
If nobody objects, I will merge the client API refactoring branch into
trunk this Wednesday.
If there are any reasons not to merge, please let me know as soon as
possible!
Cheers,
Florian
