Clinton Begin wrote:
Yikes.
Vic, with every release, we try to make iBATIS SIMPLER and SMALLER. Not bigger and more complex.
I 100% agree with you. The bigest danger to iBatis is that it gets fat or complex.
Maybe as optional packages?Sorry for jumping the gun withouth hearing the full description of your wishes, but things like remote DAO, jxm, named map dispatch, soft Hashmap cache, async exec, jdo like methods, etc. will likely not become part of the iBATIS framework.
You've been successful implementing these yourself as higher level architectural layers and external components. Hence, you are living proof that these things can (and probably should) be left out-of-scope for iBATIS.
iBATIS SQL Maps will continue to focus on one thing: Mapping SQL to Java classes/instances and the simplification of dynamic SQL processing.
iBATIS DAO will eventually be separated from SQL Maps entirely. (i.e. distributed separately).
The thing is, remote DAO is needed. No need for "narowing" ejb remote interfaces.
I talked some with the Cayene people, and they are doing remote DAO.
And.. JMX monitoring... even Tomcat comes with it, I think it's not heavy. Lik e monitor soft cache memory usage, cancel out a cache, find hits/misses %....
Definetly balance of power and simplcity is key, and better to error on side of simplicity. Those are my mottos too!
If somone gets an itch to do some of these features (in a separate package), give me a ping and I will go over my impl.
.V
Cheers, Clinton
On
