Just a head-up, compat mode is being deprecated and will be replaced by on
demand cache conversions (aka cache.getAdvancedCache.withEncodig(...))
Gustavo
On Mon, Jul 3, 2017 at 3:27 PM, Galder ZamarreƱo wrote:
> I already explained in another email thread, but let me make
I already explained in another email thread, but let me make it explicit here:
The way compatibility mode works has a big influence on how useful redeploying
marshallers is.
If compatibility is lazy, redeployment of marshaller could be useful since all
the conversions happen lazily. So,
I like it a lot.
To follow up on my comment on the PR, but to get a wider distribution,
we really need to think about how to deal with redeployments and
resource restarts.
I think restarts are unavoidable: a redeployment means dumping and
replacing a classloader with all of its classes. There
People, don't be shy, the PR is in now, but things can still change
based on you feedback. We still have two weeks until we release the Final.
On 06/29/2017 03:45 PM, Adrian Nistor wrote:
> This pr [1] adds a new approach for defining the compat marshaller class
> and the indexed entity classes
This pr [1] adds a new approach for defining the compat marshaller class
and the indexed entity classes (in server), and the same approach could
be used in future for deployment of encoders, lucene analyzers and
possilby other code bits that a user would want to add a server in order
to