Re: Really Basic Question on ServiceMix, Karaf and Camel

I'd characterize it as "ServiceMix 4 is a distribution of a number of other technologies, based on Karaf as it's OSGi framework and using Camel for EIP. One of those 'other technologies' is an instance of ActiveMQ for JMS implementation." The point is that a functionally identical installation

Re: Connecting a External ActiveMQ

If I were in Java, I'd try creating a local JMS broker and running all this code on the same machine to get started: > > > > > > > When you want to put things on the queue, use the JMS component. It will have been configure

Re: Connecting a External ActiveMQ

Try using tcp://0.0.0.0:61616 for your broker URL. If that doesn't work, from the adm machine, type "telnet 192.168.100.30 61616". You should connect and see a few lines of garbage on the screen. If you do not, check the firewalls on the machines. If the garbage comes up, try your code again

Re: Defining a CXF bus in Blueprint for use with cxfbean endpoint

On Nov 23, 2011, at 4:40 PM, Daniel Kulp wrote: > No. At that point, you start actually using parts of CXF's blueprint > support: > > http://cxf.apache.org/schemas/blueprint/core.xsd > > Use: > > http://cxf.apache.org/blueprint/core"; name="cxf"> > .. > > > > Dan Thanks Dan! After

Re: Defining a CXF bus in Blueprint for use with cxfbean endpoint

On Nov 23, 2011, at 12:05 PM, Claus Ibsen wrote: > From the XSD > http://camel.apache.org/schema/blueprint/cxf/camel-cxf.xsd > > I can see a "bus" attribute. Thanks Claus. I guess you must be talking about the element at line 54, as I mentioned that's a child of the cxfEndpoint. It seems lik

Re: Defining a CXF bus in Blueprint for use with cxfbean endpoint

On Nov 22, 2011, at 4:44 PM, Brian Topping wrote: > Hi all, > > I'd like to secure a cxfbean resource using Spring Security and SS > authorization annotations. To do so, it appears that it will

Defining a CXF bus in Blueprint for use with cxfbean endpoint

Hi all, I'd like to secure a cxfbean resource using Spring Security and SS authorization annotations. To do so, it appears that it will require adding an interceptor to the CXF endpoint as an element of a bus. So far, I have been trying to do everything in blueprint. But it doesn't appear

Re: Need help with Camel OAuth

Sorry Anita, I meant to specify the "jetty" component, although you will likely need the "gauth" as well. On Oct 10, 2011, at 3:02 PM, Brian Topping wrote: > I see, I didn't realize you were going exactly from the example. > > I ran into a couple of problem

Re: Need help with Camel OAuth

I see, I didn't realize you were going exactly from the example. I ran into a couple of problems. One was the accessibility of a java keystore file and setting up the password. This was required for the HTTPS component of the Jetty server to function. That's not documented in this example pa

Re: Need help with Camel OAuth

I just got done setting up Camel OAuth for the first time and would be happy to help. If you've ever done OAuth before, you know how hard it can be. Camel OAuth will mess with you in that case because it's so dirt simple! Anyway, could you post your routes so myself (or others) could help you?

Re: Getting an OSGi-based REST project started with Camel

ge and bundle hacking if you want to install the CXF >> bundle with Karaf or Felix from scratch. >> You can try to use the Servicemix which ships lots bundles to support the >> CXF out of box. >> >> BTW, apache CXF has it's own feature file that you can take it as

Getting an OSGi-based REST project started with Camel

Greetings, I'm interested in working with Camel under OSGi. I have previous experience with EIP and OSGi and have read the very good Camel In Action, so this seems like a reasonable leap. Over the weekend, spent some time trying some different components out. My base deployment is Felix 3.