Maybe enable dynamic import on the camel-websocket component, as a workaround.
Could be that the resource loading in camel-websocket would need to leverage the Camel API for that which has OSGi integration. On Mon, May 27, 2013 at 6:41 PM, Martin Stiborský <martin.stibor...@gmail.com> wrote: > Hi all, > I'm preparing a demo application for my tommorow talk about Apache > Camel for "Java morning coffee" session in the company where I'm > employed. (source codes and presentation to be released on github). > > I have a problem with websocket component. I can't load a html file, > neither with "file:" nor with "classpath:". > > Guys, how should be "staticResource" configured to get it working? > > -- > S pozdravem / Best regards > Martin Stiborský > > Jabber: st...@njs.netlab.cz > Twitter: http://www.twitter.com/stibi -- Claus Ibsen ----------------- www.camelone.org: The open source integration conference. Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
