Re: Configuration and IoC (Re: Proposed Roadmap for 1.3.x and beyond [long])

Don Brown wrote: When you start looking at configuration for defining procedures, it can get messy quick - just look at Jelly. Many would argue XML is just not a good fit for procedural code/definitions. Good argument. Even if you liked XML for procedural configuration, I'm not sure chain's dt

Re: Configuration and IoC (Re: Proposed Roadmap for 1.3.x and beyond [long])

Vic wrote: Don Brown wrote: When you start looking at configuration for defining procedures, it can get messy quick - just look at Jelly. Many would argue XML is just not a good fit for procedural code/definitions. Good argument. Even if you liked XML for procedural configuration, I'm not sur

Re: Configuration and IoC (Re: Proposed Roadmap for 1.3.x and beyond [long])

The bottom line is Struts now uses xml configuration as declarative configuration, rather than procedural. We define forms, actions, plugins, etc., without defining a process for using them. When you start looking at configuration for defining procedures, it can get messy quick - just look at

Re: Proposed Roadmap for 1.3.x and beyond [long]

I used to catch grief for that, but I still put it in "Best Practices". .V Dakota Jack wrote: On Sun, 21 Nov 2004 08:47:39 -0500, Ted Husted <[EMAIL PROTECTED]> wrote: Consider a "populate" method on ActionForm. From an OOP standpoint, it might be cleaner if an ActionForm populated itself rather

Re: Proposed Roadmap for 1.3.x and beyond [long]

On Sun, 21 Nov 2004 08:47:39 -0500, Ted Husted <[EMAIL PROTECTED]> wrote: > Consider a "populate" method on ActionForm. From an OOP standpoint, it might > be cleaner if an ActionForm populated itself rather than rely on an "god" > class to populate it from the outside. > Yes! This would reve

Configuration and IoC (Re: Proposed Roadmap for 1.3.x and beyond [long])

Since there was so much coming out of the ApacheCon summit, I decided to split my responses up a bit. I think long-term, the way in which Struts is configured is one of the most important factors about its ease of use and maintenance. At 9:37 AM -0600 11/21/04, Vic wrote: So I say no combined DT

Re: Moving Chain Processor Ahead (Re: Proposed Roadmap for 1.3.x and beyond [long])

Joe Germuska wrote: the ActionServlet initialize one or more catalogs meant for use with Struts and still having other things initialize catalogs for their own use. Yeah, 2 ways to init, of course. .V - To unsubscribe, e-mail: [E

Re: Moving Chain Processor Ahead (Re: Proposed Roadmap for 1.3.x and beyond [long])

Perhaps the catalog initialization belongs in the ActionServlet (via init params), so that the servlet If init catalog is in just a base class of something, than chains could be used outside of Servlet container. (One day there will be SoA containers for example). I'm not sure I follow you. In

Re: Moving Chain Processor Ahead (Re: Proposed Roadmap for 1.3.x and beyond [long])

Joe Germuska wrote: Perhaps the catalog initialization belongs in the ActionServlet (via init params), so that the servlet If init catalog is in just a base class of something, than chains could be used outside of Servlet container. (One day there will be SoA containers for example). * The cu

Moving Chain Processor Ahead (Re: Proposed Roadmap for 1.3.x and beyond [long])

At 8:47 AM -0500 11/21/04, Ted Husted wrote: While at ApacheCon, Don, Martin, and I had a chance to chat about refinements to the Struts Roadmap . Here are my notes for everyone's review and comment. Man, sounds like fun! I wish I could have been there; I'

Re: Proposed Roadmap for 1.3.x and beyond [long]

My thoughts, based on my experience, with ActionComand(Map/Context) which is full of benefits which I will list: I did something like this before Ziff, mostly to avoid a common Struts user mistake (putting properties in action class and creating a thread safety issue) such as pseudo code impl: C

Proposed Roadmap for 1.3.x and beyond [long]

While at ApacheCon, Don, Martin, and I had a chance to chat about refinements to the Struts Roadmap . Here are my notes for everyone's review and comment. As planned, in Struts 1.3.x we would integrate Struts Chain from config and add an "extends" attribut