Anonymous | Login | Signup for a new account | 11-17-2024 00:33 PST |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
0004493 | [Resin] | major | sometimes | 04-11-11 03:01 | 04-12-11 15:08 | ||||
Reporter | andreaskaltenbach | View Status | public | ||||||
Assigned To | ferg | ||||||||
Priority | normal | Resolution | fixed | ||||||
Status | closed | Product Version | 4.0.16 | ||||||
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. |
||||||||
Additional Information | |||||||||
Attached Files | BugReport.zip [^] (8,067 bytes) 04-11-11 03:01 | ||||||||
|
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
30 total queries executed. 26 unique queries executed. |