I'm one of those poor guys stuck with IBM Websphere Portal 5 and 6, which are both Java 1.4. We can still use Java 5 for the core of our application by seperating the frontend stuff into its own project, and having retrotranslator modify the core jar file before putting it into the 1.4 web application. It doesn't give you full Java 5 support, but at least its bearable and we can use generics and autoboxing.
In other words: I'm all for Wicket 1.4 on Java 5 only, the sooner the better. Jörn On Tue, Mar 18, 2008 at 8:59 AM, Johan Compagner <[EMAIL PROTECTED]> wrote: > Its not wicket that chooses for 1.4 this long. Its for example IBM > (webspere) that takes a long long time to move to jdk versions. For > example i dont think there is a webspere version in sight yet for 1.6 > and how long do we have that now? (except mac thats also a small > problem in that area) > > > > On 3/18/08, brian.diekelman <[EMAIL PROTECTED]> wrote: > > > > > > +1 for 'Option B': 1.4=generics, drop java 1.4 support > > > > This is coming from a large DoD application (notoriously behind the > > technology power curve), the only thing not generified is our UI (Wicket) > > stuff. > > > > I think maintaining 'one behind' JVM compatibility is sufficient. I mean, > > come on... Java 5 came out in 2003. > > -- > > View this message in context: > > > http://www.nabble.com/Re%3A-Planning-Wicket-Next-Generation-tp16069837p16112094.html > > Sent from the Wicket - User mailing list archive at Nabble.com. > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
