It seems like the Web Flow subproject of spring is pretty cool, especially for the age-old problem of the <back> button.
buddy On 7/8/05, Joe Germuska <[EMAIL PROTECTED]> wrote: > At 9:24 AM -0600 7/8/05, netsql wrote: > >David Whipple wrote: > >>We use it for the primarily for application assembly and integration with > >>iBATIS. > >> > > > > > >The rap on Spring is that it's a bit more complicated than Struts. > >It does have a dao interfcace, and... Struts does not. > >A big benefit is that you can switch from EJB to something else. > > > >Imo, Commons chain can be used for application assembly (and dao: > >execute(map)) > > I guess I don't understand this. commons-chain is a run-time process > (hence the API method "execute"). I suppose you're saying that you > can set properties on your commands, and thus have an assembled > application? But the Digester-based process for instantiating chains > which is provided with commons-chain is extremely limiting for > configuring business/service objects. (It's entirely possible to > construct commons chains with Spring, actually, but I don't think > that is what Vic has in mind...) > > Alternatively, you could consider population of the chain Context to > be roughly "application assembly" -- but the commons-chain library > doesn't really provide much support for setting up a complicated > Context. > > >I do wish Struts/Shale/Jakarta/Sun had an unimplemented Dao interface. > > Hm. What would this look like? Is it just a marker? The way I > write my DAOs, there would never really be any useful commonality > which could be extracted into an interface. > > Or are you talking about just the general persistence support that > Spring provides? > > Note that you can use Spring's persistence pieces (both its own > mapping framework as well as adapters to make IBATIS and Hibernate a > bit easier to use) without using Spring MVC. > > For application assembly, Spring is not complicated at all; the basic > XML syntax for instantiating beans and relating them to each other is > about as simple can be, although it can get a bit verbose sometimes. > > For Spring MVC, I can't really compare the complexity, because I've > used it so little. I found some things confusing, but it's hard for > me to tell how much of that is because I have Struts ingrained so > deeply in my brain. Also, I skipped right past Spring's basic MVC to > trying to use the recently released WebFlow package, and trying to > use it integrated with Struts, rather than just trying to build > something from scratch within its own environment. > > Joe > > -- > Joe Germuska > [EMAIL PROTECTED] > http://blog.germuska.com > "Narrow minds are weapons made for mass destruction" -The Ex > > --------------------------------------------------------------------- > 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]
