[
https://issues.jboss.org/browse/ISPN-4734?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-4734:
----------------------------------------
Actually, thinking this through, the way the filter/converter event marshaller is
configured is not the right way. In similar vein to filters and converters, we need to be
able to detect marshaller deployments. To be more precise, we could enforce
filter/converter jars to provide service definitions for Marshaller instances to use with
them. To keep it simple, if we find a marshaller in the deployment, we use it with the
filter and/or converter. If we find various, we only use the first. This makes plugging
the filter/event marshaller. Down the line, we could support deployment of marshallers in
general and plugging them to Infinispan cache.
Hot Rod marshaller for custom events...etc, needs to be configurable
in server
------------------------------------------------------------------------------
Key: ISPN-4734
URL:
https://issues.jboss.org/browse/ISPN-4734
Project: Infinispan
Issue Type: Enhancement
Affects Versions: 7.0.0.Beta2
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 7.0.0.CR1
The marshaller used by Hot Rod to marshall custom events is configurable via
HotRodServerConfigurationBuilder. This needs to be extended to server side configuration.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)