Have you tried removing the proxyInterfaces property to force spring to use CGLIB proxy to proxy the class instead of using the standard java proxies ? I 'm not sure that it will even work, but it's worth the try.
On 12/18/06, fordan <[EMAIL PROTECTED]> wrote:
Hi ! Can anyone help this. While debuging, i found out that the annotations is reflected at all. It must be something with the proxyhandling. I seems to something wrong the way spring does. Anyone tried to this before? Thanks a lot fordan wrote: > > Hi ! > > I got some problem , Can anyone Help ? Thanks Daniel > > when using an aop Proxy like this: > > Springbean.xml: > > <bean id="myService" > class="org.springframework.aop.framework.ProxyFactoryBean"> > <property name="proxyInterfaces"> > <value> > someinterface > </value> > </property> > <property name="target"> > <ref bean="implClass" /> > </property> > <property name="interceptorNames"> > <list> > <value>someInterceptor1</value> > <value>someInterceptor1</value> > <value>someInterceptor1</value> > <value>someInterceptor1</value> > </list> > </property> > </bean> > > <bean id="implClass" > class="my.implClass" > > <property name="someProperty" value="someValue" /> > </bean> > > xbean : > > <beans xmlns:jsr181="http://servicemix.apache.org/jsr181/1.0";> > <import resource="classpath:Springbean.xml" /> > <jsr181:endpoint pojo="#myService" wsdlResource="classpath:some.wsdl" > style="wrapped" /> > </beans> > > error while invoking service: > > INFO - DefaultFaultHandler - Fault occurred! > org.codehaus.xfire.fault.XFireFault: Invalid operation: > {http://www.my/ws/impl}GetSomething > at > org.codehaus.xfire.service.binding.WrappedBinding.readMessage(WrappedBinding.java:41) > at > org.codehaus.xfire.soap.handler.SoapBodyHandler.invoke(SoapBodyHandler.java:42) > at > org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131) > at > org.codehaus.xfire.transport.DefaultEndpoint.onReceive(DefaultEndpoint.java:64) > at > org.codehaus.xfire.transport.AbstractChannel.receive(AbstractChannel.java:38) > at > org.apache.servicemix.jsr181.Jsr181ExchangeProcessor.process(Jsr181ExchangeProcessor.java:109) > at > org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:490) > at > org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:442) > at > org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46) > at > org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:610) > at > org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174) > at > org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:176) > at > org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134) > at > edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665) > at > edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690) > at java.lang.Thread.run(Thread.java:595) > > -- View this message in context: http://www.nabble.com/Invalid-operation-while-invoking-a-JSR181-endpoint-tf2822150s12049.html#a7927539 Sent from the ServiceMix - User mailing list archive at Nabble.com.
-- Cheers, Guillaume Nodet
