Yes, considering refactoring for an IOC container is on the RoadMap for 1.4.
* http://struts.apache.org/roadmap.html Both Don and I have had excellent luck refactoring for Spring, as has Matt Raible. It's Craig's first preference for Shale, and I believe the BeeHive crew is using it. Seems the obvious choice. :) The very cool part is that, if you are careful, you can keep the IOC container decoupled from the application, making it possible to plug a different one in. -Ted. On Fri, 18 Mar 2005 09:52:07 -0600, Joe Germuska <[EMAIL PROTECTED]> wrote: > At 10:30 AM -0500 3/18/05, Ted Husted wrote: > >On Fri, 18 Mar 2005 08:05:50 -0600, Joe Germuska <[EMAIL PROTECTED]> wrote: > >> I don't really understand this use case. unless the contents of > >> <html:form> are hyper-dynamic, you'd need the same form bean to back > >> it, even if upon submit the thing actually goes to a different > >> action. I am familiar with the use case that would change the > >> destination of the "action" property of the form using JavaScript, > >> but I think you're talking about something different. > > > >It's less about the formbean and more about what the mapping does. > > ah. of course. do you recall any of the issues raised around the > earlier ticket you mentioned? > At 7:08 AM -0500 3/18/05, Ted Husted wrote: > >** There was an old ticket for a taglib enhancement that would let us > >"back" all the attributes with a JavaBean. There was a cold reception > >at the time, but I keep thinking it might be a good way to pass in > >whateverr attributes people might need without resorting to RTEs > > Then you wrote: > >** An IOC container might be helpful if implemeting a taglib backing bean.. > > Do you dare suggest that Struts' endorsement of an IoC container also > be slated for 1.4? ;-) > > It might be helpful, but it also seems far from a requirement, if the > bigger question becomes contentious. > > Joe --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
