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

TO:Banq

EJB 太过重量级了，除非是重用性很高的组件，否则，成本太高。

说实在的，我又用回以前的老方法了，将数据逻辑的处理放在了 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.

Cheers

-Wanchun

我们就谈谈它的安全设置，它的出发点是非常好，希望能让权限设置更简单，通过配置解决，它实际是想实现一个方便的权限配置系统，好像你以前也提到过这样的项目。　目前其实我也在做这样的系统，和它不同的是，我不是依附在J2EE或EJB这个框架上，也不同于ofbiz，它依赖于Entity engineer和Service engineer，　我觉得这两个依附体都太虚。

我依赖的树型结构的节点，我以前帖子说了，很多应用，包括网站Portal或电子政府等工作流系统，都离不开一个基本核心，节点Node,依附Node来开发一个动态可扩展的权限系统，我相信不会错，同时使用Java的JAAS，我查了一下sf.net关于这个的项目，还都在立项正在进行中，

目前我已经完成1/2的系统，我会引入NodeLet概念，NodeLet实际就是挂在一个Node上功能块，类似Portlet，比如可以是一个论坛，或其他。

对全系统的role设计已经进入尾声，从个人感觉，role设计真是一个基础知识，不精通role，很多项目就不可能做好，很多项目的失败就是role设计的失败。

In fact, I'm not good at Java UI too. ^_^ And this is my first time to develop a Java UI application which is so complex.

It's really hard to understand the whole java ui framework. But I'm free these days. So, I can learning every day.

I believe Jbuilder is the most popular IDE for Java applications. So, you will not wast you investments on it. And it's fast enough.

I'm very glad to hear that you have solved browser printing problem. Congratulation!.

关于EJB是否重量，正是我之前说的，这也是目前Java世界讨论的最热点，我们在这里也就不必争论，你选择JDBC也是很多人选择了EJB之后的“回归”，无可厚非，其实不管是否使用EJB，数据库连接包括直接JDBC都是浪费性能的，因此Cache是必选。

因此，Cache有几个方向：

1. 针对底层结构cache,　我上次贴了一篇文章，就是关于做JDBC的cache优化，至于这样优化cache是否有效，仁者见仁了。

2. 针对应用的Cache，　我认为这才是提高性能Cache的真正效力所在，但是因为每个应用都不不一样，就不大可能在底层做个通用的Cache机制，只能靠架构设计师在各自实际项目进行良好的设计。

因此，如果在我们中大型项目中，有一个良好的Cache机制，那么底层架构使用EJB还是JDBC或JDO已经不是很重要，区别我认为不会很大。