I'm having trouble configuring a jsr181 proxy, with the error messages indicating that the required context bean cannot be found.
I include a clause such as the following in the SU configuration xbean.xml file, then startup Servicemix 3.1 (using "./bin/servicemix ./conf/servicemix.xml"). Deployment yields a warning that no bean called "context" can be found. <jsr181:proxy id="myId" context="#context" service="myns:myService" type="com.mycompany.myproject.MyClass"/> I have read posts that indicate that the context bean is automatically created when the SU is deployed. Is this true always? Does it make a difference if servicemix is executed as a standalone app, or itself deployed within a web container? In the ./conf/servicemix.xml file, the jbi container configuration is identified by "#jbi". I did wonder if using a clause such as this might be more appropriate: <jsr181:proxy id="myId" container="#jbi" service="myns:myService" type="com.mycompany.myproject.MyClass"/> I have tried both of these without success. Does the version make a difference? If it doesn't work in 3.1 does it work in the latest version from the repository? Regards, Callum. -- View this message in context: http://www.nabble.com/Jsr181-proxy-tf3788321s12049.html#a10713260 Sent from the ServiceMix - User mailing list archive at Nabble.com.
