Please no jakarta-commons-collections-3.1.jar in Kodo 3.2!!

Question

As far as I know jakarta-commons-collections-3.1.jar is not backward
compatible with 2.x version of jakarta collections. Many things (such as
Struts) are shipped with collections 2.1 and might not work with 3.1
collections. Is it possible to keep 2.1 collections in Kodo. And eventually
get rid of it all together if possible! IMHO jakarta collections (and lang?)
libraries are bad dependency since they can't keep it backward compatible
and went through 3 versions of it in short time

Answer 1

Use servlet filter to clean up your PMs
1. Create Disposable interface
2. Create PMHolder which implement Disposable and make sure when you create
instance of PMHolder you attach it to http request as an attribute (I
suggest passing request as parameter to PMHolder constructor and
autoregister new instance with the request)
3. Create filter which inspects all request attributes and call
Disposable.close() on all attributes which implement Disposable
It will let you create PMs lazily in your struts forms and not to worry
about closing them and it will let you to use PMs directly in your JSPs if
you have to again without worry about leaks
"Tim Holloway" <[email protected]> wrote in message
news:[email protected]...
Abe White wrote:
http://jakarta.apache.org/commons/collections/compatibility.html
Also commons beanutil have a new version which can run against both 2.1and
3.x codebases. I think there is lots of confusion in thius area. We
trued
our struts apps with 3.1 collections they seem to be ok.
Thanks for the link! It's particularly good to hear that struts seems towork
with 3.1.If it didn't, I'd be in deep trouble. I've got a major webapp using Struts
1.1 which I rewrote using KodoJDO. The only tricky part was allowing for
pages that would gather data from 4 or 5 places (some of them collections)
and push them out to the view, since I needed to release the Persistence
Manager in the Struts Action Processor or I'd either have to put logic on
the JSPs or leak Persistence Managers.
// Disconnect display data from PM so we can close PM.
pm.makeTransient(info);
pm.makeTransient(info.getOfacMain());
pm.makeTransientAll(info.getOfacMain().getOfacAddress());
pm.makeTransientAll(info.getOfacMain().getOfacAlias());
pm.makeTransient(info.getOfacSourceData());
pm.close();
I did have issues about a large browse set, but Stephen Kim set me on the
right track on that one.
Kodo 3.2 Beta didn't have any Struts-related problems either.
Tim Holloway
EverBank