While i agreed to Jeff's request of seeing how this can be externalized
with some minimal refactoring to ibatis 2, FWIW i still thought it is fair
to the ibatis users/community (especially those who dont know anything
about SQLJ which one can safely assume is the majority) about what this
patch means, since folks are still voting...
1- Absolutely no change to the way you build and use ibatis applications.
You wont see/feel anything change.
2 - There wont even be an additional jar (SQLJ.jar) that will be forced
down your throat to download and keep on your machine or to satisfy
compile/runtime dependencies.
3- It is a simple 3 java files with no external dependencies that get added
to ibatis source code.
thanks
Mario
Clinton Begin
<clinton.be...@gm
ail.com> To
iBatis Java Mail List
24/01/2009 00:35 <[email protected]>
cc
Please respond to Subject
user-j...@ibatis. [VOTE] Should iBATIS support SQLJ?
apache.org
Hi everyone,
A group of developers have approached us with a contribution of code
to patch iBATIS so that it supports SQLJ.
If you've never heard of SQLJ, here are two links...
http://en.wikipedia.org/wiki/SQLJ
http://www.google.com/trends?q=sqlj
The future of SQLJ is not clear to me, nor is its adoption rate over
time. Certainly iBATIS has a broader user base than SQLJ does.
So the question is: Should we support SQLJ as a feature of iBATIS?
+5 == Absolutely... iBATIS will be better for it.
+1 == Yes, support SQLJ.
0 == Doesn't matter to me.
-1 == No, keep them separate.
-5 == No way. iBATIS is better off without it.
This vote will remain open for 72 hours.
Cheers,
Clinton
