Perhaps the catalog initialization belongs in the ActionServlet (via init params), so that the servlet
If init catalog is in just a base class of something, than chains could be used outside of Servlet container. (One day there will be SoA containers for example).
I'm not sure I follow you. In a base class of what? If I understand the recent changes to commons-chain, where there is a single CatalogFactory per classloader, then there's nothing incompatible with having the ActionServlet initialize one or more catalogs meant for use with Struts and still having other things initialize catalogs for their own use.
* The current chain project is a lot of classes.
?? I think Struts-Chain was VERY CLEAN. I saw it and was humbled. Maybe we are talking about 2 diferent things.
It's clean, but it still has 41 classes. It's not a big deal to me, but especially since half those classes are in either the "servlet" or "legacy" packages, and thus theoretically not destined for a long life in Struts, I wondered if we would want to handle it in some other way than importing them all into the core. Also, I have a hint of an idea that it would be cool to be able to have a JAR with a chain config in it that was kind of self-configuring (something like what Don has recently enabled for other config files), and I wanted to see if that resonated with anyone else.
Joe
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Narrow minds are weapons made for mass destruction" -The Ex
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
