On 11/26/2013 4:17 PM, Christian Helmbold wrote:
>> John D. Ament <john.d.am...@gmail.com> 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

Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
Resteasy-users mailing list

Reply via email to