23:02:33] <roamer323> dain - the config store as it exists
today is completely dependent on Java serialization - is that
correct?
[23:02:44] <dain> yes
[23:04:22] <roamer323> the idea of an LDAP config store
provider - and deserializing on different platform/VMs ... is that a
far-future-release thing?
[23:04:52] <dain> yes
[23:05:06] <dain> well if you do it then you can have it right
away :)
[23:05:47] <roamer323> haha :-) I was actually still thinking of
the client container bit - was considering to write a config
provider that spits out spring.xml
[23:05:59] <roamer323> ... BUT... it seems it is too late to do it
after builder
[23:06:15] <roamer323> because the attribute info is lost and
the GBean has already been initialized.
[23:06:50] <dain> well if you look at the
GeronimoServiceFactory in the gbean code
[23:07:08] <dain> I have code that converts a geronimo
gbeandata into a spring bean definition
[23:07:39] <dain> for most beans you should be able to take the
resulting bean definiton and write it to a spring.xml file
[23:07:59] <dain> the only problem will be if any of the attributes
are complex objects
[23:08:10] <roamer323> does the gbeandata get persisted to
the config store as kinda annotation? Or do I tap into it further
up-stream?
[23:08:27] <dain> in that case you would have to write some
custom code to convert the complex attributes to spring bean
definitions
[23:09:14] <dain> the stuff written to the .ser file is determined
by code in the geronimo Configuration class
[23:09:24] <dain> I'll get you a link....
[23:09:30] <roamer323> ok
[23:10:30] <dain> take a look at the storeGBeans method
[23:10:31] <dain>
http://svn.apache.org/viewcvs.cgi/geronimo/trunk/modules/kernel/src/java/org/apache/geronimo/kernel/config/Configuration.java?rev=190011&view=markup
[23:10:53] <dain> and the loadGBeans method
[23:12:31] <roamer323> thanks for the pointers - I'll take do
some exploration.