Yes, I know. If you want to figure out how dependency injection should look/work, why not go with the "standard"? You can use the full-blown CDI crap or just do the javax.inject stuff by itself.
On Mon, Mar 21, 2011 at 9:51 AM, Marshall Schor <[email protected]> wrote: > CDI = Context and Dependency Injection, a new J2EE 6 feature. > > -Marshall > > On 3/21/2011 9:12 AM, James Carman wrote: >> How about just use the new CDI stuff? That's what it should look like. >> >> On Mon, Mar 21, 2011 at 8:19 AM, Marshall Schor <[email protected]> wrote: >>> >>> On 3/18/2011 4:09 PM, Alex Chaphiv wrote: >>>> Hi, >>>> >>>> I have several annotators that require objects that are rather complex to >>>> build. >>>> I've been able to get around this using by using ExternalResources with >>>> custom >>>> api interfaces, but it requires a lot of boilerplate and doesn't allow for >>>> sharing of dependencies between ExternalResources. >>> Could you share what an "ideal" solution might look like, along with a >>> small, >>> made-up sample of code that would use this ideal solution (with enough >>> comments >>> for wide understanding :-) )? >>> >>> Something that showed how the boilerplate is shrunk, and how dependencies >>> are >>> specified? >>> >>> -Marshall Schor >>>> So what would be the best way to get around this? Even better, is there >>>> any >>>> support for Spring or Guice? >>>> >>>> >>>> >> >
