Repackaged?
As opposed to just use their jar?
Would it have same "package" in case I use OGNL outside, class collision
for versions?
Or would it be like org.ibatis.ognl.* so no collision?
I guess I would just include the jar, kiss. I know depedency, etc. but
my 2 c.
Also I hope we no longe
(read-only=false does not cache).
So serialize="true" works, but not all the time. I spent a few hours and
could not find a pattern of when/why it works sometimes and sometimes
not. The code patch works 100% of time for those that want that effect.
I propose that in addition to docs, the code
Docs I think say make read-only false, not leave true.
So this is what I have:
which works in most cases, but sometimes it does not.
So what is it read-only=false as per docs or what you said?
tia,
.V
Larry Meadors wrote:
Make the cache read-only and serializable, and it will be container wi
y Meadors wrote:
Make the cache read-only and serializable, and it will be container wide.
Larry
On Fri, Jul 11, 2008 at 9:56 AM, Vic Cekvenich <[EMAIL PROTECTED]> wrote:
Before:
protected ThreadLocal localSqlMapSession = new ThreadLocal();
After:
protected static ThreadLocal loc
Before:
protected ThreadLocal localSqlMapSession = new ThreadLocal();
After:
protected static ThreadLocal localSqlMapSession = new ThreadLocal();
in SqlMapClientImpl
Rationale:
People(me) expect the cache to be "container"(war) wide, and not
"session" based. Ex: I have user1 pull put client 101,
'ello dev list.
is ibatis 3 in svn ok to use for alpha?
(is it still kiss?)
any rumors as to what it will be/have/eta?
also, plz consider using memCached for default cache.
;-)
.V