I just reply to your post about DAO gen in separate thread, try Velocity, actually I just finished a generator myself.
you use XML to model the object, can have whereclause, relationship, and some business rules( formula, constraint) stuff, there get translated into java object with simple getter/setter, constraint, relationship enforcement.
I use Velocity. I did found a tool that can gen object from database schema directly( I can find it for you if you care), but I need add lots of things before gen.
BTW, do you guys have yahoo messager?
The title here led me to that website, I like his idea "Simple", that's what exactly My Topas trying to solve with J2EE.
Yes, I have the same confusion about his technology, too me, it has some cute stuff but maybe over-stated to my opinion.
I think he is using some kind reflection to hook client to his sejbObject which is not exposed as EJB, which is not new( JMX, Proxy all do the same thing). I have little doubt about its performance under heavy load. But the idea is same as Topas, I use a GenericFacade Bean to brigde the client and server.
He definitely see the problem of declaring security in EJB, so he push all security control into one file or database, that's practical approach, in fact I did the same thing in topas
I am not impressived with his distribution, in topas I call it "Service routing", it's not a first class feature, in certain cases, it can be very useful, but generally its useless or hurt perofrmance if use it blindly.
In summary, its product has some nice things and cover a lot of ground, should we invite him into our discussion? I really want to shot him a emal.
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.
To Banq, 100% about your point on cache, there is no sinle pattern can be applied universally, so it's always a tough job to get it done right on complex system.
Glad to hear that the progress on your security framework, but I feel your target is far beyond simply enforce security for main stream business applications, It's for auth controlling type applications or for applications that have extensive exposure to hierachical management, flow control etc.
Just one wish, make sure it's easy pluggable to third party system,(Topas has only a simply security config, but I will create a interface call BanqSecurityContext to be integrated in future) Oh, it should be 100% bug free ;-)
Good to get your confirmation on jbuilder popularity, I guess that's why you intend to use Jbuilder as IDE for plug.
I wish I have more free times, all my times in past month are sucked into preparing for next EAI system(In China), especially on XML transformation performance issues. but so far I have no confidence about their(developers) acceptance of using XML.