|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
_______________________________________________ weld-issues mailing list [email protected] https://lists.jboss.org/mailman/listinfo/weld-issues
My initial idea was to combine both approaches Weld uses for resource injection. That would be combining InjectionServices (EE) (http://docs.jboss.org/weld/reference/latest/en-US/html/ri-spi.html#injection.services) with granular resolution services e.g. JpaInjectionServices (EE_INJECT) (http://docs.jboss.org/weld/reference/latest/en-US/html/ri-spi.html#d0e6542) However I do not think that this a good idea any longer.
So if we called InjectionServicesImpl#aroundInject every time before reading the injected reference from the static field, would this work for GF? This would require GF to clean up the static field eventually but otherwise should be fine. All we need to do is to change the docs of InjectionContext.getTarget() to reflect that this method may actually return null when this is the static case.
WDYT?