[JBoss JIRA] (ISPN-12045) Clarify jboss-marshalling deprecation message
by Ryan Emerson (Jira)
[ https://issues.redhat.com/browse/ISPN-12045?page=com.atlassian.jira.plugi... ]
Ryan Emerson updated ISPN-12045:
--------------------------------
Sprint: DataGrid Sprint #46 (was: DataGrid Sprint #46, DataGrid Sprint #47)
> Clarify jboss-marshalling deprecation message
> ---------------------------------------------
>
> Key: ISPN-12045
> URL: https://issues.redhat.com/browse/ISPN-12045
> Project: Infinispan
> Issue Type: Enhancement
> Components: Server
> Affects Versions: 11.0.0.Final
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 11.0.1.Final
>
>
> Currently the server always warns that jboss has been deprecated as it's necessary for the module to be on the classpath of the server in order to provide transcoding of `x-jboss-marshalling` MediaType.
> {code:java}
> WARN (main) [org.infinispan.PERSISTENCE] ISPN000554: infinispan-boss-marshalling dependency detected, jboss-marshalling has been deprecated and will be removed in the future
> {code}
> We should update the wording so that it simply states "jboss-marshalling is deprecated and will be removed in the future"
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 8 months
[JBoss JIRA] (ISPN-12144) Operator Docs: Clarify xsite docs
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-12144?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-12144:
-----------------------------------
Sprint: DataGrid Sprint #46, DataGrid Sprint #47 (was: DataGrid Sprint #46)
> Operator Docs: Clarify xsite docs
> ---------------------------------
>
> Key: ISPN-12144
> URL: https://issues.redhat.com/browse/ISPN-12144
> Project: Infinispan
> Issue Type: Enhancement
> Components: Documentation
> Reporter: Donald Naro
> Assignee: Donald Naro
> Priority: Major
>
> describe that XSite need the operator to work properly and show within the doc how it works
> XSiteRepl DG8.1 is done with a single site master the "xsite-service" will forward all requests to the JGroups coordinator
> the site-master is choosen by operator and the jgroups coordinator is used
> operator will query all pods and tag the pod where coordinator run
> if the coordinator dies, the operator finds the new coordinator/pod and tags that one. the service automatically updates and starts using the new pod
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 8 months