Well, the free time isn't all back yet, but since I think there might be some discussion first, I thought I'd post and get things rolling so that by the time I do have free time, I'm ready to rock.
I'm not entirely sure what the difference between a struts-toolkit and Ted's Scaffold project would be, but then (gasp) I haven't really explored Scaffold too deeply. Also, one of the pieces which I had planned to put in the kit got added to the Struts core, so now I'm left with PlugInSupport (http://demo.jgsullivan.com/struts/PlugInSupport.html) and... well, one of the other developers has done a lot on a ComposableRequestProcessor, but it may be moot if the struts-chain proposal comes to the fore... so I'm not sure that there's enough to really flesh out a toolkit unless other folks have ideas.
I'm also just wondering what the rules would be for importing stuff into net.sf.struts.* packages. It seems like there should be some general agreement on what belongs in the kit, or how people offer stuff.
Ideas?
Joe
-- -- Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "If nature worked that way, the universe would crash all the time." --Jaron Lanier
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Struts-apps mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/struts-apps
