First to Iceant, 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.
To Banq, 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.