Re: [Resteasy-users] How to setup RESTEasy with CDI and Netty?

[John D. A. <joh...@gm...>]

Bill,

Actually from looking at the current impl, I have a fairly small
trivial change.  It would only work in CDI 1.1 though.  I could
probably implement it using reflection to avoid the compilation
change, if you're interested in taking the contribution.  This would
use standard CDI look up in an SE environment.

John

On Tue, Nov 26, 2013 at 6:06 PM, Bill Burke <bb...@re...> wrote:
>
>
> On 11/26/2013 4:17 PM, Christian Helmbold wrote:
>>
>>
>>
>>
>>
>>
>>> John D. Ament <joh...@gm...> schrieb am 20:23 Dienstag,
>>> 26.November 2013:
>>>>
>>>> I assumed this would happen, based on Bill's email.
>>
>>
>> You're right. This happend after adding the following line to my startup
>> code:
>>
>>
>> deployment.setInjectorFactoryClass(org.jboss.resteasy.cdi.CdiInjectorFactory.class.getName());
>>
>>> you'll probably
>>> need to extend the CdiInjectorFactory to use your own BeanManager.
>>
>>
>> I wonder why
>> http://docs.jboss.org/resteasy/docs/3.0.5.Final/userguide/html_single/index.html#d4e2034
>> seems to be so simple.
>>
>> Sounds like Weld and RESTEasy are simply not built for what I want to do!
>> The philosophie seems to be: use the whole application server or use
>> something else. My idea was to create a small configuration which could be
>> restarted very fast during development. I've done something similar with
>> Guice and Jersey. But Wildfly should start pretty fast, so this could be
>> better than trying to do the configuration myself.
>>
>
> I would dive into this, but I don' thave the cycles at this time.  Its just
> a matter of gettin Weld initialized in a SE environment, and then tweaking
> the CdiInjectorFactory.
>
>
> There is a Resteasy Guice adapter too.
>
>
>
> --
> Bill Burke
> JBoss, a division of Red Hat
> http://bill.burkecentral.com