On 27/09/2011 01:26, aedwards wrote:
I know this is late on this post... but This would be a nice feature.
Curious if there has been any progress?
Also, another really great feature would be if the camel-web application
could use the jmx endpoints to communicate with camel-contexts so that the
web application could be deployed separately from the camel deployments.
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-web-contexts-tp4418412p4843495.html
Sent from the Camel - Users mailing list archive at Nabble.com.
My patch for CAMEL-3519 (which has not yet been accepted, I hope because
it's large rather than because it's rubbish) provides support for
multiple contexts.
It's currently slated to be fixed in 2.9.0, so I hope someone will
manage to review it before then.
One of the unfortunate side-effects of leaving a large patch for quite a
long time is that it'll almost certainly need some work to account for
changes since I wrote it.
One of my aims was to abstract out the source of camel contexts, so they
could be found by different providers - one being within the war and the
other being OSGi.
There is nothing to stop a provider being written that uses JMX
exclusively, though as it stands this would require an alternative
compilation (only one provider can be used).
Also, my work in this area is incomplete - although the providers are
used to find the contexts they are not always used for accessing them -
I left this out in order to keep an already large patch small.
So I'd say it would be an entirely achievable task to make an
alternative camel-web binary that works via JMX exclusively, but it's
not there yet.
Jim
