MalformedObjectNameException when starting camel context

2012-12-30 Thread Tim Dudgeon
I'm seeing a strange error when starting a camel context. Its dependent on the machine I'm running on. On one machine (Windows) the same context and simple route runsfine, but on a different machine (Mac) the context fails to start. The key part seems to be this: javax.management.MalformedObj

Fork/join with resequencing

2012-12-30 Thread Vincent Lombart
Hello all, I am trying to implement a fork/join process where work is read by a single thread, distributed to several parallel threads then joined back to another single thread. I am using Camel SEDA components for interfacing between threads. The single thread at the end must process the messages

Re: MalformedObjectNameException when starting camel context

2012-12-30 Thread Willem Jiang
Hi, It looks something is wrong with you host name. Can you just change it? Willem 在 2012-12-30,下午11:45,Tim Dudgeon 写道: > I'm seeing a strange error when starting a camel context. Its dependent on > the machine I'm running on. On one machine (Windows) the same context and > simple route ru

Re: MalformedObjectNameException when starting camel context

2012-12-30 Thread Liam Clarke-Hutchinson
Hi Tim, It's trying to get an mbean or similar with a name derived from (I guess) your machine's IP - which is in IPV6, hence lots of colons. However, if you look at the documentation for ObjectName (http://docs.oracle.com/javase/1.5.0/docs/api/javax/management/ObjectName.html) you'll see it stat

Re: cxfrs(authentication and authorization)

2012-12-30 Thread Jason Chaffee
I think there are a number ways you could to it. 1) If you wanted to secure your routing and/or do it at the camel route level then you could use camel-shiro. See http://camel.apache.org/shiro-security.html Or camel-spring-security. See http://camel.apache.org/spring-security.html 2) You

Re: Proxy BeanInvocations turning into first-class payloads?

2012-12-30 Thread Liam Clarke-Hutchinson
Hmm, I think I've figured this out. The CamelProxyFactoryBean uses ProxyHelper to create the proxied service - but the "convert a bean invocation with one arg to just the arg" logic requires using the PojoProxyHelper to create the proxied service, as it's using a different invocation handler. So,