> -----Original Message----- > From: Rickard Öberg [mailto:[EMAIL PROTECTED] > > Jason Carreira wrote: > > Sort of, but it's not used that way. > > In what way is it not used as a cache?
In the way in which if it doesn't find it in the runtime configuration it fails back to the programmatic configuration and in the way in which you don't invalidate and regenerate a piece of it. > You're assuming that they're all configured with XML. The > example I gave > showed how the subapps were registered using XML, but their > configuration could be loaded from whatever. > Sorry, I was really going off on a tangent because I didn't want to forget to ask about the entity resolver again. > Now, there's another approach to that (as I think I have mentioned > before). We could say that the ONLY way to configure XWork is through > XML. But, it would be entirely possible to have an entity > resolver that > creates XML from another configuration format or source. That > way we'd > need pluggable entity resolvers instead of pluggable configuration > providers. > > Not sure which approach is best though. Any thoughts on that? > I think pluggable configuration providers are better. Writing code to build PackageContexts in code from a resultset is easier and more straightforward, IMHO. Jason ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
