cayenne-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dzmitry Kazimirchyk (JIRA)" <>
Subject [jira] [Closed] (CAY-2065) Pluggable serialization and connectivity layers for ROP
Date Wed, 02 Mar 2016 12:55:18 GMT


Dzmitry Kazimirchyk closed CAY-2065.
       Resolution: Fixed
         Assignee: Dzmitry Kazimirchyk
    Fix Version/s: 4.0.M4

The changes from the pull request on github were applied. 

The summary of changes is as follows:
* ROP is not using Hessian RPC mechanism any more, instead there is a simple HTTP servlet
which parses request parameters to determine action to perform and request body as the serialized
ClientMessage object;
* Hessian usage is now limited to serialization/deserialization logic;
* New interfaces ROPSerializationService and ROPConnector responsible for serialization and
connectivity respectively are now configurable and replaceable through DI module configuration.

I've updated the upgrade notes with the instructions on migrating to new ROP servlet class
and added this task to the release notes.

> Pluggable serialization and connectivity layers for ROP
> -------------------------------------------------------
>                 Key: CAY-2065
>                 URL:
>             Project: Cayenne
>          Issue Type: Improvement
>          Components: ROP
>    Affects Versions: 4.0.M3
>            Reporter: Dzmitry Kazimirchyk
>            Assignee: Dzmitry Kazimirchyk
>             Fix For: 4.0.M4
> Currently ROP relies solely on hessian for both connectivity and serialization. This
is starting to cause troubles because hessian library is now effectively abandoned with nobody
to address arising issues, e.g. inability to serialize JSR-310 date types (CAY-2038), HTTP
keep-alive not working in HessianConnection.
> The goal of this task is to rework ROP to have hessian independent connectivity layer
and separate hessian serialization layer which both will be replaceable and configurable through

This message was sent by Atlassian JIRA

View raw message