I use velocity to generate special framework code too.
To use xml is an good idea. But I'm doing sth to improve the coding efficiency. I think GUI is a good choice here.
BTW: Here is my yahoo_messenger #: pengchen_iceant
说实在的，我又用回以前的老方法了，将数据逻辑的处理放在了 Store Procedure 中， 毕竟一个 SQL 就完成的东西，实在没必要去浪费那么多的网络资源，而且我相信在数据库本地做操作，要比在Java中做效率高,事务处理也好控制。
you are really versatile, a friendly UI is always the desired things, unfornately ( my Java UI experience == null) always return true. So I use XML editor for data modeling.
Are you doing someone to integrate with Jbuilder? Maybe we are doing similar thing now( actually it's a friend of mine, a java client expert), the idea is after define object model(meta-data) in XML, we generate database ddl, java objects and make the meta-data available in Jbuilder, with our design time resolver and dataset provider, jbuilder programmer can build multi tier app just as easy as client/server database app. challenge is we just start to use jbuilder, may not quite fully understand how people use it, another concern is market, I certainly hope jbuilder is the No.1 IDE for building java client, otherwise my investment is wasted.
I am sure you are not promoting store procedure, but I agree it's very popular and practical in many situations.
Oh, thanks again for the tip of browser printing, if you got chance to Hainan, buy a insurance at airport, the policy is printout use a activeX control.