As Nicklas suggests, add META-INF/org.jboss.weld.enableUnsafeProxies file to your deployment.

On Sep 26, 2012, at 1:03 PM, Charles Moulliard <cmoullia@redhat.com> wrote:

Hi Ales,

Can you explain a little bit please as I don't understand what you exactly suggest to do ?

Regards,

Ir. Charles Moulliard
Sr. Enterprise Architect | RedHat, Inc
cmoullia@redhat.com | mobile: +32 473 604 014 | RedHat.com
skype: cmoulliard | twitter: @cmoulliard
blog: cmoulliard.blogspot.com
On 26/09/12 11:05, Ales Justin wrote:
Wonder if the marker mentioned in 


does anything? Or perhaps the deployment stops at a validation phase before it gets that far...

Both - validation and instantiation - use the same mechanism, this InstantiatorFactory.
It was just re-writen a bit, to be per app, not per whole Weld.
So, if IF knows how to instantiate w/ arg ctor, you should be fine.

-Ales

On Wed, Sep 26, 2012 at 10:39 AM, Charles Moulliard <cmoullia@redhat.com> wrote:
Hi.

Is there a workaround to avoid to add a non args constructor in an abstract class when we get this error "WELD-001435 Normal scoped bean class org.apache.camel.builder.BuilderSupport is not proxyable because it has no no-args constructor " ?

Regards,

--
Ir. Charles Moulliard
Sr. Enterprise Architect | RedHat, Inc
cmoullia@redhat.com | mobile: +32 473 604 014 | RedHat.com
skype: cmoulliard | twitter: @cmoulliard
blog: cmoulliard.blogspot.com

_______________________________________________
weld-dev mailing list
weld-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-dev



--
---
Nik
_______________________________________________
weld-dev mailing list
weld-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-dev



_______________________________________________
weld-dev mailing list
weld-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-dev

_______________________________________________
weld-dev mailing list
weld-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-dev