Skip to content
This repository was archived by the owner on May 28, 2018. It is now read-only.

Conversation

@vetler
Copy link
Contributor

@vetler vetler commented Sep 17, 2014

Updated documentation to make it explicit that resources must be Spring components in order for Spring proxying to work, and also created test cases to make sure Spring proxying actually works as expected.

This is just a partial fix for the discussion in JERSEY-2112. The original report seems to be the fact that it is not obvious that the resources must be annotated @Component (or similar). However, there is another bug that makes it impossible to use this on filters and providers - this is not handled by this pull request.

Copy link
Collaborator

Choose a reason for hiding this comment

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

please use <literal> instead of <code>

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixed.

…must be Spring components in order for Spring proxying to work

Updated documentation to make it explicit that resources must be Spring components in order for Spring proxying to work, and also created test cases to make sure Spring proxying actually works as expected.
mpotociar added a commit that referenced this pull request Oct 20, 2014
Contributed partial fix for JERSEY-2112.
@mpotociar mpotociar merged commit 5a0552a into javaee:master Oct 20, 2014
AdamLindenthal pushed a commit that referenced this pull request Oct 22, 2014
Change-Id: Id2db76276d6dbb6092cbdfbd68c0c52dbb7d3ec3
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants