Hi,
There are several pieces of code that are located in the Cactus project (namely in our Ant integration module) and which could be useful to others independently of the Cactus context:
1- an API to manipulate the web.xml deployment descriptor (read and write). 2- an API to start/stop containers 3- an API to create container configuration
- API 1 is useful to any container writer in particular. Thus I believe containers like Geronimo must probably already have such an API. I'll ask on the Geronimo mailing list to check it out. If they do, and if this API is nicely packaged in a thin jar (a jar used to manipulate servlet deployment descriptors for example), would you be ok to have Cactus Ant integration depend on it?
This is mainly a very light layer on top of the DOM for *rewriting* deployment descriptors. Containers get away with just reading, which is much simpler. I don't really think container writers would have interest in this code, but I might be wrong.
- For 2 and 3, what would you think about creating a Jakarta Commons project/a Codehaus project or possibly a Geronimo subproject for that? It could be called something like "Container Client Interface" (CCI). I'm not sure yet how much time I'll have for this but I'd like to know what you think so that we have some direction on what we'd like to achieve.
Ah, deja vu ;-)
I don't really see a need to factor out this code "just for the fun of it". If there are potential clients other than Cactus that express interest in participating in the further development of the code, sure. But if not, we only create extra work for the Cactus contributors, with the single benefit of having cleaned up project scope a bit.
Not that I'm against code reuse in any way: I just don't like splitting up code bases only because it seems logical in theory, while in the real world the same guys keep working on the code, only now they have to track more CVS modules, manage releases and websites of more products, etc.
Cheers, Chris -- Christopher Lenz /=/ cmlenz at gmx.de
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
