Re: [webbeans-dev] jsr299-utils

I'm happy to start work on it, but I don't want to step on someone else's work. Has any work on the SPI changes been allocated?

-Clint On Sat, May 23, 2009 at 12:32 PM, Gavin King <gavin.king(a)gmail.com&gt; wrote: > We need an impl of the SPI as soon as possible, since we need to know > if there's any bugs in it :-) > > On Sat, May 23, 2009 at 5:07 AM, Clint Popetz <cpopetz(a)gmail.com&gt; wrote: >> Matt, >> >> Thanks, 11.4 in the spec (BeanManager.createInjectionTarget and >> InjectionTarget.inject) is exactly what I need. >> >> So, who's implementing that, and what's the time frame for it? I can >> do that, if no one's scheduled it do it. >> >> -Clint >> >> On Fri, May 22, 2009 at 11:03 PM, Matt Drees <matt.drees(a)gmail.com&gt; wrote: >>> Oops, meant to send that to the list, not just Clint. >>> Sorry for the dup, Clint. >>> >>> -Matt >>> >>> On Fri, May 22, 2009 at 11:58 PM, Matt Drees <matt.drees(a)gmail.com&gt; wrote: >>>> >>>> Before you go too far down this road, you might want to get a new draft of >>>> the spec from Gavin. Recently an SPI was added specifically for injection >>>> into third-party objects, so I don't think the project you're proposing >>>> needs to exist. >>>> >>>> -Matt >>>> >>>> >>>> On Fri, May 22, 2009 at 6:34 PM, Clint Popetz <cpopetz(a)gmail.com&gt; wrote: >>>>> >>>>> I'm investigating how to best move non-contextual injection into a >>>>> webbeans extension that's jsr299-impl independent. While I could >>>>> rewrite a stripped down version of the reflection scanning/caching >>>>> code that is already used by the existing webbeans-specific >>>>> non-contextual-injector, but it wouldn't be as performant or compliant >>>>> as the code that's already in the core, and I'm wondering if it's >>>>> reasonable to try to break out this chunk of the core into a library >>>>> which my extension (and possibly others in webbeans-extensions) uses. >>>>> >>>>> These would be some coherent self-contained subset of >>>>> org.jboss.webbeans.{injection, introspector, introspector.jlr,bean, >>>>> metadata, util}. I think of this as the part of the core that >>>>> examines classes and builds a metamodel about the beans they >>>>> represent, and knows how to inject them, but doesn't deal with >>>>> contexts, bootstrapping, and the zillion other things the core does. >>>>> I think it could probably be made implementation-independent based on >>>>> the jsr299-api. It would have to be made independent of ManagerImpl, >>>>> mainly. >>>>> >>>>> It couldn't live in webbeans-extensions obviously, since the core >>>>> would depend upon it. But if it lived in webbeans-model, then >>>>> webbeans-core could depend on it, as could jsr299-utils. >>>>> >>>>> Thoughts? This is not terribly well investigated yet, so those with >>>>> more experience with the source base, feel free to wave me off. I >>>>> just hate duplicating code. >>>>> >>>>> Thanks, >>>>> -Clint >>>>> >>>>> -- >>>>> Clint Popetz >>>>> http://42lines.net >>>>> Scalable Web Application Development >>>>> _______________________________________________ >>>>> webbeans-dev mailing list >>>>> webbeans-dev(a)lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/webbeans-dev >>>> >>> >>> >>> _______________________________________________ >>> webbeans-dev mailing list >>> webbeans-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/webbeans-dev >>> >>> >> >> >> >> -- >> Clint Popetz >> http://42lines.net >> Scalable Web Application Development >> >> _______________________________________________ >> webbeans-dev mailing list >> webbeans-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/webbeans-dev >> > > > > -- > Gavin King > gavin.king(a)gmail.com > http://in.relation.to/Bloggers/Gavin > http://hibernate.org > http://seamframework.org >