David,
This sounds really interesting. If you have the time, can you give a
brief explanation of what
xbean-reflect
xbean-finder
is and how they are used?
Regards,
Alan
David Blevins wrote:
On Aug 22, 2006, at 1:47 PM, Jacek Laskowski wrote:
Hi,
The subject says it all - where/how's XBean used in OpenEJB 3?
So far, I've worked in the xbean-reflect module (which I love) in a
few places, assembly and protocol creation IIRC. We use the
xbean-finder all over. And Dain did the xbean-spring work, which
gives us an alternate way to assemble OpenEJB. Definitely some work
that can be done there -- the xml format is still in prototype stage
and could be improved.
There are a couple modules of OpenEJB origin that were seeded when
XBean was at Codehaus, xbean-telnet and xbean-classpath. Both were
moved over so ActiveMQ, ServiceMix and others could use them. The
xbean-telnet module which is based on our telnet code and has since
been cleaned up a bit by Hiram for ActiveMQ -- he's pretty good at
making things look organized. The xbean-classpath module is based on
a chunk of our embedding cod; the part that can shove classes into the
classpath "forcefully" if needed. Always been meaning to work those
back in.
Is anyone working on using more features of XBean in OpenEJB3 (if
there's any left out ;-))?
I'm not currently working on anything, but I hope to start prototyping
an idea i had a couple weeks ago where we put ".xbean" files in our
server directories that say what they are (conf dir, beans dir, logs
dir, libs dir) and we wouldn't have to assume they were named a
specific thing or in a specific location anymore. People could put
the directories where ever they wanted, or in some cases (libs and
beans) have as many of them as they want. Still a rough idea in my
head and I have the urge to make it capable of doing a lot more, such
as a general-purpose metadata system. You never really know till you
start working on it.
Shall I
expect more to come or do I need to roll up my sleeves and do it
myself? ;-)
Both :) Overall, it's a "scratch your itch" based system. So if you
have an itch, you're encouraged to scratch it :)
As long as there are ideas, there'll be code to write and consume :)
-David
Jacek
--Jacek Laskowski
http://www.laskowski.net.pl
