This discussion accidently became private, back to the list...
Kees Jongenburger wrote: > <quote> > So, I think your point may be valid, but I think it may not be very much related to > my proposal, > unless you are saying that we can actually pass generic java-objects around for any > configuration, > and that the ResourceLoader could produce such objects (parsing the XML's completely > genericly and > so on). Such completely generic memory objects are perhaps parsed InputSources (dom > Documents?), but > I don't think that you hint at that. There may, btw, also be configuration resources > which are not > XML at all. > </quote> > > Hmm , perhaps you are right finding resources must be seen appart from getting > configurations. A > configuration framework would just "use" the resource loader. It might be a good > idea possible to > make it possible to store the configuration in a resource builder. When I think of > the apps2 > project you often want to add and alter mmbase resources how do you think this will > be done. Wil > the resourceloader provide an outputstream? Perhaps yes. I was looking into the URL object, you can do openConnection().getOutputStream(). Perhaps you can write in that way to the resource.. Otherwise, you could perhaps add specialzied functions to the ResourceLoader like 'persistifyResource(InputStream)' or so, and it can write it then to a location it knows it can read again. Michiel -- Michiel Meeuwissen mihxil' Mediacentrum 140 H'sum [] () +31 (0)35 6772979 nl_NL eo_XX en_US
