- Tuesday 8th December - New York at the Hyatt Hotel in New York City
- Thursday 10th December - San Francisco at the Hyatt Hotel in Burlingame
If you're in the area pop by and say hello - you'll need to register on the above links.
We'll have a bunch of presentations on various popular open source Apache projects like ActiveMQ, Camel and ServiceMix. Schedule in the links above. See you there if you can make it!
Here's a flavour of what to expect, the devoxx talk I did recently.
I'll be there! ;)
I was there and it was a great session.
I totally forgot to ask you about XBean which has been bothering me for years!
Yes, I could have found online docs and read (except that there weren't many), but it looked like it was going away and ActiveMQ configuration wouldn't have to make any mention of it. My thesis was brilliant, but it was also incorrect ...
Active MQ in Action makes mention of XBean and that book is current (i mean ... it still hasn't been released ... how could it NOT be current?).
So, is there going to be an XBean in action? Why does Apache have such a thing for XBean?
Thank you for tolerating me.
XBean was created way before Spring 2.0 came into existence to allow Spring XML to be extended with custom namespaces. (XBean does a bunch of other IoC/container stuff that the Geronimo project was looking to use too).
Then Spring 2 came along and added support for pluggable namespaces (such as Camel & ActiveMQ XML).
On the Camel project we went with the approach of using JAXB beans for the XML configuration; this has an added benefit that its easy to read an XML configuration, process it and write it out again too etc.
So Camel doesn't use XBean at all. Eventually we'll probably replace the XBean stuff on ActiveMQ with JAXB as well.
So from a Camel/ActiveMQ perspective I'd not worry too much about XBean other than its the implementation right now of how the ActiveMQ Xml configuration works in Spring.
Post a Comment