+1 I think moving to Java 1.5 provides the opportunity to improve Click in lots of ways: * introduce annotations to enable more explicity autobinding, and move away from using public scoped page variables * introduce typed collections in the Click API * enable better support for Spring integration (stereotype) * fix up Cayenne 3.0 integration issues with JDK 1.4 compiled Click classes
regards Malcolm Edgar On Sat, Apr 18, 2009 at 12:32 AM, jschmidt <[email protected]> wrote: > > >>> Oh, but I *am* using JDK6 with Click. But I use the provided jars >>> instead of the sources provided by Click. The libs are obviously >>> compiled with 1.4 to be compatible. If I want to run Click as "native" >>> JDK6, I would have to include the sources in my project and compile them >>> myself. >>> >>> But I don't know if I want that. Should I? >> Yes. It's very simple: >> 1. checkout >>http://incubator.apache.org/click/docs/developer-guide/source-code.html >> 2. build http://incubator.apache.org/click/docs/developer-guide/building.html >> >> In fact you might need to, e.g. if you are using Cayenne 3 (with the >> click integration). > > Exactly :). If you want to use Cayenne 3 you *need* to recompile Click with > it (and a JDK >= 1.5). > Cayenne 3 relaxed some signatures, so some base methods simply won't work > anymore - it happened to me too (deletion of entities was not working > anymore). > However if you recompile, it will work, but you also need to apply locally > the patch from this issue: > https://issues.apache.org/jira/browse/CLK-505 > otherwise the default click build.xml will compile it against the old > signature from Cayenne 2. > > Joseph. > > -- > View this message in context: > http://n2.nabble.com/Click-JDK-5-tp2647818p2651057.html > Sent from the click-user mailing list archive at Nabble.com. > >
