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

Ensure priority of Serialization packages #377

Merged
merged 1 commit into from Aug 12, 2011
Merged

Conversation

@acdesouza
Copy link

@acdesouza acdesouza commented Aug 8, 2011

Ensure priority of Serialization packages: first 3rd party, then br.com.caelum.vraptor.restfulie.serialization last br.com.caelum.vraptor.serialization.

As explained: http://groups.google.com/group/caelum-vraptor-dev/browse_thread/thread/a2856c64c311d17a

…om.caelum.vraptor.restfulie.serialization last br.com.caelum.vraptor.serialization.
@lucascs

This comment has been minimized.

if you do this, .serialization and .restfulie.serialization have the same priority. The idea is that restfulie.serialization must be before .serialization.

EDIT: it is done by the method below (refactor it?)

This comment has been minimized.

Copy link
Owner

@acdesouza acdesouza replied Aug 8, 2011

Yep. As the name, should, suggest ;)

@lucascs

This comment has been minimized.

maybe parameterizing this package comparator would be better... creating a protected method that returns a Comparator, so people can override it

@acdesouza

This comment has been minimized.

Here, Comparator handles priority to restfulie.serialization, when compared to vraptor.serialization.

lucascs added a commit that referenced this pull request Aug 12, 2011
Ensure priority of Serialization packages
@lucascs lucascs merged commit b08a2bb into caelum:master Aug 12, 2011
@lucascs
Copy link
Member

@lucascs lucascs commented Aug 12, 2011

Thank you =)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants
You can’t perform that action at this time.