On Sun, 04 Apr 2004 09:04:24 -0600, Joe Germuska wrote: >> IMO, Struts datasource handling should be deprecated and removed. >> It had it's place in the past but now Struts has no business >> "managing" datasources; that's the containers job and most of >> them do it better than Struts. I would like part of Struts 2.x >> to focus on simplifying users' lives and removing this feature >> follows in that spirit; but that may be for another thread. >> > > Well, I was thinking about doing this refactoring in a pre 2.x > timeline and maintaining compatibility. But I agree that > datasource handling should be left out of Struts.
It's important to note that the DataSource manager is not managing the underlying implementations in the way a container would, but making them available through a "catalog" interface. This component just takes whatever datasource instances it is handed and retains the references as a list. Before deprecating and removing anything like this, we should create a standalone version that people could plugin. I am quite certain many people still use it and 1.x is suppose to be backward compatible. Someone could add it to the legacy package, or find some other home for it. But, personally, I'd say removing it would seem to be more trouble than leaving it be. Unlike our ill-fated datasource implementation, the manager is zero maintenance. :) -Ted --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
