[MGNLREST-229] Jersey REST dispatcher impl only registers providers under package info.magnolia.rest Created: 14/Feb/20 Updated: 07/Jan/21 Resolved: 16/Mar/20 |
|
| Status: | Closed |
| Project: | Magnolia REST Framework |
| Component/s: | None |
| Affects Version/s: | 2.1.5 |
| Fix Version/s: | 2.1.6, 2.2 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Mikaël Geljić | Assignee: | Mikaël Geljić |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 1d 3h | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||
| Date of First Response: | |||||||||
| Sprint: | 6.2 Ramp-up 17, 6.2 Ramp-up 18, 6.2 Ramp-up 19, 6.2 Ramp-up 20 | ||||||||
| Story Points: | 1 | ||||||||
| Description |
|
—say we add a filter from another Magnolia module, we're screwed; In general, the jersey dispatcher impl scanning by package is sub-optimal, and thus may not play nice with @Providers from customer projects; it also doesn't seem to leverage the additionalProviders from rest-integration module config. RESTEasy impl otoh doesn't seem to restrict any root-package, but provider-scanning is to be verified there too. |
| Comments |
| Comment by Marc Johnen [ 07/Jan/21 ] |
|
I think this issue is not resolved. A custom writer still only works if the package starts with info.magnolia . |
| Comment by Mikaël Geljić [ 07/Jan/21 ] |
|
Hi marc.johnen, are you using Jersey or RESTEasy? Do you register your provider with META-INF file or Magnolia's additionalProviders configuration? EDIT: iirc, the info.magnolia package restriction applying to Jersey is to mitigate potential interference from other providers sitting on the classpath. |