One (rather pointed) question: Being that RequestProcessor is one of the primary extension points for the Action servlet, how will this new API affect HTTPS protocol handling? I assume that the SSLExt library will have to be completely rewritten, or are you guys planning on rolling that functionality into Struts 1.3?
Well, SSLExt would continue to work, but it won't "inherit" new functionality like the ability to configure an action path with a chain command to be executed as part of the request process. That was implemented using a chain command, and I didn't see the point in also retrofitting the original RequestProcessor with that behavior.
I've just started working on the idea of Struts-specific sub-interfaces to the commons-chain Context. I've solicited some review and feedback on the dev list (interested parties see http://issues.apache.org/bugzilla/show_bug.cgi?id=5395)
Once those are stable, then I think it should be open season on adapting any existing RequestProcessor libraries into Command form, which I think should be pretty straightforward. I think SSLExt-type support would be totally appropriate in the Struts core, and I think other committers have said similar. There might be some small organizational questions about where to put the SSL taglibs, since we've factored the Struts taglibs into a separate build artifact, but that's manageable.
If anyone feels like taking it on, contributions are always welcome!
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]
