Well, not really a CXF bug as there really isn't anything we can do about it.  
(I think)

<jaxws:endpoint> doesn't create a proxy for anything.    It creates a concrete 
subclass of Endpoint.   If you are seeing for it, that is Spring's auto proxy 
stuff kicking in and doing some sort of wacky JDK5 proxy object wrapping.   


Dan


On Tue May 5 2009 2:04:33 pm nicolas de loof wrote:
> I allready have @Ressource annotation injection support in my
> spring-context (it is automatically enabled by <context:component-scan>)
>
> Moving the @Resource to a setter fix the issue (as only Spring will support
> this).
>
> Changing <aop:* and <tx:* to use proxy-target-class=true also fix this
> issue as another option.
>
> Anyway this sounds like a CXF bug to me, isn't it ?
>
> 2009/5/5 Karthik Abram <[email protected]>
>
> > Try the following:
> > Add <bean
> >
> > class="org.springframework.context.annotation.CommonAnnotationBeanPostPro
> >ces sor"/>
> >
> >
> > -----Original Message-----
> > From: nicolas de loof [mailto:[email protected]]
> > Sent: Tuesday, May 05, 2009 4:39 AM
> > To: [email protected]
> > Subject: @Resource injection fails in 2.2.1
> >
> > Hi
> > I'm using <jaxws:endpoint to expose my web services, generated using
> > wsdl2java :
> >
> >  <jaxws:endpoint address="/consultation/1.0"
> > implementor="#consultationEndPoint"
> > wsdlLocation="wsdl/consultation_v1.0.wsdl"/>
> >
> >  <bean id="consultationEndPoint" class="com.foo.ConsultationEndPoint" />
> >
> >
> > My EndPoint uses @Resource annotation to get Spring business-layer beans.
> > I get an error on CXF 2.2.1 :
> >
> > Caused by: java.lang.IllegalArgumentException: Can not set
> > com.foo.ConsultationService field com.foo.ConsultationEndPoint.service to
> > $Proxy176
> > at
> >
> > sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(Unsa
> >feF ieldAccessorImpl.java:146)
> >
> > The resource injector seems to use the proxy generated by
> > <jaxws:endpoint> for resource injection and not the implementor bean.
> >
> >
> > Nicolas

-- 
Daniel Kulp
[email protected]
http://www.dankulp.com/blog

Reply via email to