Skip to content

Conversation

@artembilan
Copy link
Member

JIRA: https://jira.spring.io/browse/INT-3337

  • Introduce MessageReadingMongoConverter (similar to MongoDbMessageStore.MessageReadingMongoConverter)
  • Change tests to use ConfigurableMongoDbMessageStore with MessageReadingMongoConverter

Copy link
Contributor

Choose a reason for hiding this comment

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

I am not so sure the rename will be necessary.

Copy link
Member Author

Choose a reason for hiding this comment

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

Why? My position to remove MongoDbMessageStore as redundant.
And when we will have just only ConfigurableMongoDbMessageStore, there might be a question: "And where is a plain MongoDbMessageStore? What is a reason to call it as 'Configurable', if there is no other implementation ?"

Copy link
Contributor

Choose a reason for hiding this comment

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

I just don't see any compelling reason to inflict any pain on users; assuming they take heed of the deprecation, they will change their apps to use the configurable store; why would we force them to do another rename late? It just seems unnecessary to me.

I am not terribly concerned either way (whether we decide to do it or not), but I see no reason to include the ...will be renamed... in the JavaDocs.

Copy link
Member Author

Choose a reason for hiding this comment

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

OK. I won't mind to leave it as is and don't rename.
If it is only one concern here, I'll push the fix soon.

Copy link
Contributor

Choose a reason for hiding this comment

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

I didn't finish my review yet; let me take another look this morning.

@garyrussell
Copy link
Contributor

Otherwise LGTM

@artembilan
Copy link
Member Author

Pushed

1 similar comment
@artembilan
Copy link
Member Author

Pushed

Copy link
Contributor

Choose a reason for hiding this comment

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

private ctor() ?

Copy link
Member Author

Choose a reason for hiding this comment

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

Sure!

@artembilan
Copy link
Member Author

Pushed as we discussed privately:

  • Revert any changes
  • move *Message converters to the MongoDbMessageStore
  • Add tests

Artem Bilan added 5 commits March 28, 2014 17:35
JIRA: https://jira.spring.io/browse/INT-3337

* Introduce `MessageReadingMongoConverter` (similar to `MongoDbMessageStore.MessageReadingMongoConverter`)
* Change tests to use `ConfigurableMongoDbMessageStore` with `MessageReadingMongoConverter`
* Add for `MessageDocumentMongoConverter` custom `converters` for all known `Message<?>` type
* Add `MessageDocumentFields`
* Add support to store/read `ErrorMessage`. As a trick for `Throwable` is selected (de)serializing converter
@artembilan
Copy link
Member Author

Pushed _id for MessageWrapper and ACAware for MMS

Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe we should go ahead and rename as we discussed before MessageDocumentMongoConverter.

Copy link
Member Author

Choose a reason for hiding this comment

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

Keep in mind here it has name MessageWrapper and we can't change the name for backward compatibility.
From other side MessageReadingMongoConverter is an inner class, so its name doesn't have value too.

Copy link
Contributor

Choose a reason for hiding this comment

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

np;

@garyrussell
Copy link
Contributor

Need to update the docs to reflect the differences between the 2 stores; currently

The MongoDbMessageStore remains for backward compatibility and may be removed in future releases.

@artembilan
Copy link
Member Author

But we have in doc a difference comment. However I won't mind to add the note regarding removal in the future.

@artembilan
Copy link
Member Author

Pushed

Copy link
Contributor

Choose a reason for hiding this comment

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

Do you get a warning for this? Eclipse doesn't complain when the @Id annotation is present.

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes, IDEA complains

Copy link
Contributor

Choose a reason for hiding this comment

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

OK; LGTM; merging.

@garyrussell
Copy link
Contributor

Merging with these fixes.

@garyrussell
Copy link
Contributor

Merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants