I am following %SERVICEMIX_SRC%\servicemix-jsr181\src\test\resources\proxy\xbean.xml to package my SA named JsrProxyAssembly. My xbean.xml is:
<beans xmlns:sm="http://servicemix.apache.org/config/1.0"; xmlns:jsr181="http://servicemix.apache.org/jsr181/1.0"; xmlns:http="http://servicemix.apache.org/http/1.0"; xmlns:test="http://test";> <classpath> <location>.</location> </classpath> <!-- START SNIPPET: proxy --> <jsr181:endpoint annotations="none" service="test:echoService" serviceInterface="test.Echo"> <jsr181:pojo> <bean class="test.EchoProxy"> <property name="echo"> <jsr181:proxy service="test:EchoService" context="#context" type="test.Echo" /> </property> </bean> </jsr181:pojo> </jsr181:endpoint> <!-- END SNIPPET: proxy --> <jsr181:endpoint annotations="none" service="test:EchoService"> <jsr181:pojo> <bean class="test.EchoService" /> </jsr181:pojo> </jsr181:endpoint> </beans> When I send a SOAP request to ESB, it reaches till test.EchoProxy, but cannot proceed further and getting the following error: Starting Apache ServiceMix ESB: 3.1-incubating-SNAPSHOT Loading Apache ServiceMix from file: servicemix.xml INFO - ConnectorServerFactoryBean - JMX connector available at: service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi INFO - JBIContainer - ServiceMix 3.1-incubating-SNAPSHOT JBI Container (ServiceMix) is starting INFO - JBIContainer - For help or more informations please see: http://incubator. apache.org/servicemix/ WARN - ManagementContext - Failed to start rmi registry: internal error: ObjID already in use WARN - ManagementContext - Failed to start jmx connector: connector:name=rmi INFO - ComponentMBeanImpl - Initializing component: #SubscriptionManager# INFO - DeploymentService - Restoring service assemblies INFO - JBIContainer - ServiceMix JBI Container (ServiceMix) started INFO - AutoDeploymentService - Directory: install: Archive changed: processing servicemix-http-3.1-incubating-SNAPSHOT-installer.zip ... WARN - AutoDeploymentService - Shared libraries servicemix-shared are not installed yet: the componentservicemix-http installation is suspended and will be resumed once the listed shared libraries are installed INFO - AutoDeploymentService - Directory: install: Finished installation of archive: servicemix-http-3.1-incubating-SNAPSHOT-installer.zip INFO - AutoDeploymentService - Directory: install: Archive changed: processing servicemix-jsr181-3.1-incubating-SNAPSHOT-installer.zip ... WARN - AutoDeploymentService - Shared libraries servicemix-shared are not installed yet: the componentservicemix-jsr181 installation is suspended and will be resumed once the listed shared libraries are installed INFO - AutoDeploymentService - Directory: install: Finished installation of archive: servicemix-jsr181-3.1-incubating-SNAPSHOT-installer.zip INFO - AutoDeploymentService - Directory: install: Archive changed: processing servicemix-lwcontainer-3.1-incubating-SNAPSHOT-installer.zip ... WARN - AutoDeploymentService - Shared libraries servicemix-shared are not installed yet: the componentservicemix-lwcontainer installation is suspended and will be resumed once the listed shared libraries are installed INFO - AutoDeploymentService - Directory: install: Finished installation of archive: servicemix-lwcontainer-3.1-incubating-SNAPSHOT-installer.zip INFO - AutoDeploymentService - Directory: install: Archive changed: processing servicemix-shared-3.1-incubating-SNAPSHOT-installer.zip ... INFO - ComponentMBeanImpl - Starting component: servicemix-jsr181 INFO - ComponentMBeanImpl - Initializing component: servicemix-jsr181 INFO - jetty - Logging to [EMAIL PROTECTED] via org.apache.servicemix.http.jetty.JCLLogger INFO - ComponentMBeanImpl - Starting component: servicemix-http INFO - ComponentMBeanImpl - Initializing component: servicemix-http INFO - ComponentMBeanImpl - Starting component: servicemix-lwcontainer INFO - ComponentMBeanImpl - Initializing component: servicemix-lwcontainer INFO - AutoDeploymentService - Directory: install: Finished installation of archive: servicemix-shared-3.1-incubating-SNAPSHOT-installer.zip INFO - AutoDeploymentService - Directory: deploy: Archive changed: processing httpbind-sa.zip ... INFO - ServiceAssemblyLifeCycle - Starting service assembly: HttpBindAssembly INFO - ServiceUnitLifeCycle - Initializing service unit: HttpBind INFO - ServiceUnitLifeCycle - Starting service unit: HttpBind INFO - jetty - jetty-6.0.1 INFO - jetty - Started SelectChannelConnector @ localhost:8081 INFO - AutoDeploymentService - Directory: deploy: Finished installation of archive: httpbind-sa.zip INFO - AutoDeploymentService - Directory: deploy: Archive changed: processing jsrproxy-sa.zip ... INFO - ServiceAssemblyLifeCycle - Starting service assembly: JsrProxyAssembly INFO - ServiceUnitLifeCycle - Initializing service unit: JsrProxy INFO - ServiceUnitLifeCycle - Starting service unit: JsrProxy INFO - AutoDeploymentService - Directory: deploy: Finished installation of archive: jsrproxy-sa.zip ERROR - DefaultFaultHandler - Fault occurred!org.codehaus.xfire.XFireRuntimeException: Could not find operation setContext in the service model. at org.codehaus.xfire.wsdl11.parser.WSDLServiceConfigurator.visit(WSDLServiceConfigurator.java:229) at org.codehaus.xfire.wsdl11.parser.WSDLServiceConfigurator.configure(WSDLServiceConfigurator.java:198) at org.codehaus.xfire.service.binding.ObjectServiceFactory.create(ObjectServiceFactory.java:223) at org.apache.servicemix.jsr181.xfire.JbiProxy.getProxy(JbiProxy.java:91) at org.apache.servicemix.jsr181.xfire.JbiProxy.create(JbiProxy.java:59) at org.apache.servicemix.jsr181.xfire.JbiProxyFactoryBean.getJBIInvocationHandler(JbiProxyFactoryBean.java:80) at org.apache.servicemix.jsr181.xfire.JbiProxyFactoryBean.access$000(JbiProxyFactoryBean.java:46) at org.apache.servicemix.jsr181.xfire.JbiProxyFactoryBean$1.invoke(JbiProxyFactoryBean.java:70) at $Proxy0.echo(Unknown Source) at test.EchoProxy.echo(EchoProxy.java:38) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.xfire.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:54) at org.codehaus.xfire.service.binding.ServiceInvocationHandler.sendMessage(ServiceInvocationHandler.java:271) at org.codehaus.xfire.service.binding.ServiceInvocationHandler$1.run(ServiceInvocationHandler.java:84) at org.codehaus.xfire.service.binding.ServiceInvocationHandler.execute(ServiceInvocationHandler.java:132) at org.codehaus.xfire.service.binding.ServiceInvocationHandler.invoke(ServiceInvocationHandler.java:107) 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:107) at org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:479) at org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:439) 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) I assume I am doing something wrong in my xbean.xml, since I am exposing even the proxied service using jsr181:endpoint. But the example in servicemix test folder also deosn't give any hint on how to configure test.EchoService as the service to which JBI-Proxy has to be created. Can anybody give me the correct configuration for this? NB: My ultimate aim is to solve this requirement: http://www.nabble.com/Invoking-External-Webservice-tf2495197s12049.html TIA - Mike -- View this message in context: http://www.nabble.com/jsr181%3Aproxy---A-Doubt--How-2-configure-Proxied-Service--tf2596089s12049.html#a7241216 Sent from the ServiceMix - User mailing list archive at Nabble.com.
