Sgarlata Matt wrote: >>Attached is a first cut at creating a ChainServlet. Committers, > please feel >>free to add this to CVS (you'll need to add the license, version #s, >>and change the package declaration), to modify it, or to tell me what >>to do to modify it (and I will do so).
Can we change it to look for the catalog as a resource on the classpath, instead of under the file root? Since the Catalog is a business layer component, it may often be maintained as part of the business classes, and may even be distributed in a JAR. [At least mine is :)]
I think both options would be helpful -- enough Struts users are confused about where to put application resources files that we should probably support either.
Other than that, I've it up and running now in my application now.
I put it in a package under web/servlet/config. Does that sound reasonable?
I also added a static to the Catalog interface to provide a convenient standard for the Catalog attribute name. This will help keep various concrete implementations on the same page.
In addition to ChainServlet, I've also got a ChainListener (implements ServletContextListener, for Servlet 2.3 or later systems) that scans all the JAR files in WEB-INF/lib for "META-INF/chain-config.xml" files and processes them automatically -- pretty much the same way that a container automatically recognizes TLD files in JARs. With this, you can just drop in a JAR with the appropriate config and all your commands get recognized. It'll get committed as soon as I build a test case for it, but that's the reason for the "servlet23.present" flag in the build.xml I checked in last night.
If anyone needs motivation to step up to a Servlet 2.3 or later container, consider this a push in the right direction :-).
-Ted.
Craig
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
