|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 4493 | major | sometimes | 04-11-11 03:01 | 04-12-11 15:08 | |
|
|
|||||
| Reporter: | andreaskaltenbach | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | 4.0.16 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 4.0.17 | ||
|
|
|||||
| Summary: | 0004493: UnsatisfiedResolutionException inside CDI extensions | ||||
| Description: |
Given the following setup: -One JAR, containing one CDI-managed bean -Second JAR, containing a second CDI-managed bean which gets bean of first JAR injected Starting up Resin works as intended, no problems so far. --- When we add the following CDI extension, Resin fails with an UnsatisfiedResolutionException when calling event.getBean().getInjectionPoints(): public class MyExtension implements Extension { void processManagedBean(@Observes ProcessManagedBean<?> event) { // comment this line and Resin will startup without any problems event.getBean().getInjectionPoints(); } } --- Jersey 1.6, for example, calls the same method inside its CDIExtension so that Jersey 1.6 does not work together with Resin 4.0.16 out of the box. Enclosed, you'll find a tiny example Maven project which reproduces the bug. Note that Resin startup up successfully, when we comment the extension line shown in the code snippet above. |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: |
|
||||
| Notes | |||||
|
|
|||||
|
|
||||