Comments on: Generic OGNL Controller without Spring WebFlow

By: hydraulic car jack

hydraulic car jack — Sat, 14 Mar 2009 12:45:25 +0000

This is the first time I comment here and I should say you give us genuine, and quality information for other bloggers! Good job.
p.s. You have a very good template . Where did you find it?

By: dhaval

dhaval — Fri, 04 Apr 2008 05:59:12 +0000

respected viewers,
i wnat to know that can we use more than one command(Entity) class in controller in spring.

By: simaer

simaer — Fri, 14 Mar 2008 00:41:38 +0000

By: Robert Sayfullin

Robert Sayfullin — Mon, 22 Jan 2007 12:05:58 +0000

I absolutely agree with you about the fact that any practice in software development is arguable. I personally was many times disappointed on my memory, Eclipse’s refactoring and Spring WebFlow when changes of method signatures were not reflected in 20K blah-blah-flow.xml.
But there is other side. If you look at typical small webapp you will see that it looks like onion in part that deals with CRUD and other trivial functionality.
You wrap getHibernateTemplate in DAO, DAO in manager, manager in service, services are used in controllers. Good practice definitely. However sometimes if we know that all this functionality will be just set of wrappers and you never gonna change ‘getObjectById’ signature we can sacrifice our habits and break some rules. Then and only then such weird stuff as Generic managers or Generic OGNL controllers are allowable.

By: Alexey

Alexey — Mon, 22 Jan 2007 08:46:33 +0000

The standard argument against moving code to XML is the future manageability (adding some type-unsafe scripting to strict language) and dumbness to automatic refactoring. If you rename or change the signature of the updateProfile() method you’ll have to manually rename/change it in your spring config file. IDEA will probably cope with renaming but not with changing signature.
Actually I don’t see why writing these several lines in XML config is easier than writing a two-line java class. And what advantages it brings to you other than creating one class less?