I think doing the compatibility layer after the code is imported in to Apache makes sense. WebWork has various developers who go in spurts of involvement. The two core developers are Jason and myself. Lately, there have been about 3 or 4 others pretty actively involved, but I'm sure they wouldn't mind going through the normal process to get commit access again after the merger.

On Nov 30, 2005, at 11:06 AM, Don Brown wrote:

Joe Germuska wrote:
There isn't directly, and this was one of the first additions I made to WebWork when I started Struts Ti. In WebWork, the servlet dispatcher does everything prior and including identifying the Action, then hands it off to the interceptor chain. My code in Struts Ti replaced this with a servlet that hands off to a RequestProcessor, which used Commons Chain to perform all the preprocessing.

I plan to be adding this back in shortly after we import the WW code base.
I'd been meaning to follow up on this. I think you, or someone, briefly floated the idea of building the Struts compatibility layer at OS.org before doing the import.

I have mentioned it before, although I don't know if it was me you are thinking of specifically. WebWork could support Actions and ActionForms pretty easily, I believe, evidenced by their existing ModelAware interceptor which supports the model as a different object than the action.

If it was you, I assume you've changed your mind? If it wasn't you, no bother -- I think the better approach is to bring it here. Presumably the Struts committers are going to heavily involved in the compatibility, so if for no other reason, it will be easier for us to work on that in an Apache.org repository.
How many WebWork committers are there, anyway?

Patrick and Jason, then 3 or four others. Patrick, you want to add anything here?

Don

Joe


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to