Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ISPN-1475 - Clean up state transfer and rehashing configuration options #833

Closed
wants to merge 2 commits into from

Conversation

danberindei
Copy link
Member

I moved all the common state transfer settings to a separate stateTransfer
element and I deprecated the old settings.

I then added the chunkSize setting to the new stateTransfer element.

I moved all the common state transfer settings to a separate stateTransfer
element and I deprecated the old settings.

I then added the chunkSize setting to the new stateTransfer element.
@galderz
Copy link
Member

galderz commented Jan 16, 2012

@danberindei Looking at the code... in the mean time, you probably wanna add a section in https://docs.jboss.org/author/x/OoASAQ stating the configuration changes?

@galderz
Copy link
Member

galderz commented Jan 16, 2012

@danberindei Where are the corresponding xsd changes? Please note that you need to add xsd documentation too.

@@ -23,10 +23,17 @@
/**
* Configures how state is retrieved when a new cache joins the cluster. Used with invalidation
* and replication clustered modes.
* @deprecated Use {@link #stateTransfer()} instead.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This goes back to what I said in the email about marshallerClass - These xBuilder classes are new in 5.1, so I don't see the new to deprecate anything. Simply map how it used to be done with 5.0 config and how this is done now in 5.1. This applies to new StateRetrievalConfigurationX classes too. I'd just get rid of them.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought it would be kind of nasty to keep the old configurations right until the last CR and only remove them in the FINAL.

@maniksurtani, do you agree with removing the deprecated config directly or should I keep them?

@maniksurtani
Copy link
Member

@danberindei @galderz +1on catching the XSD thing. Thanks @galderz .

@danberindei
Copy link
Member Author

@galderz sorry about the missing xsd + documentation, coming right up

I updated the XSD with the new stateTransfer element.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants