Re: wicket 1.5 build is failing because of 1.6 deps...
Exactly! Also those organizations, which want to stay with very old and normally unsupported software versions usually budget for extra support. Java 1.5 is not supported normally any more by Sun, so they will be bying Sun "retirement" support anyway or running all their business systems on unsupported software. Similarly old version wicket support can be provided as extra service. I am sure there will be organizations willing to sell it, if there will be enough demand for it. So, I am for letting the developers make the choice ... On 12/22/2009 11:19 AM, Erik van Oosten wrote: I am afraid you miss the most important argument: whether the core developer *want* to develop with Java 5. Its mostly their free time and love they put in Wicket, we should never forget that. (Of course they probably want to have users, etc. But in the end it is their decision.) Regards, Erik. Neil Curzon wrote: -1 to JDK 1.6 The possibility of excluding even 1% of potential users for the negligible benefit of using 1.6-specific features would be a bad decision. 1.5 is simply the right jdk to be developing frameworks in for now. Pro 1.6 crowd: Understand that the argument is not that anybody's organization *should* stay with JDK 1.5, but that some organizations *will* stay at 1.5 regardless of whether you think they should be up to date. If the jump from 1.5 to 1.6 was as big as the jump from 1.4 to 1.5, I would be firmly in the pro-1.6 camp, but the benefits just aren't worth the costs.
1.4.2 upgrade problem
I believe there is a bug in wicket 1.4.2, which stopped me from upgrading :(
I have created issue for this:
https://issues.apache.org/jira/browse/WICKET-2519
Finally I narrowed it down to adding following to quick start, which
works fine in 1.4.1 and fails in 1.4.2:
2 lines to HomePage.html
key="logout" />
/>
2 lines to HomePage.java
add(new BookmarkablePageLink("logout", HomePage.class));
add(new BookmarkablePageLink("login", HomePage.class));
and HomePage.properties
login=Login
logout=Logout
I get following stack trace
WicketMessage: Could not find child with id: login in the wicket:enclosure
Root cause:
org.apache.wicket.WicketRuntimeException: Could not find child with id:
login in the wicket:enclosure
at
org.apache.wicket.markup.html.internal.Enclosure.checkChildComponent(Enclosure.java:210)
at
org.apache.wicket.markup.html.internal.Enclosure.ensureAllChildrenPresent(Enclosure.java:249)
at
org.apache.wicket.markup.html.internal.Enclosure.onComponentTagBody(Enclosure.java:169)
at org.apache.wicket.Component.renderComponent(Component.java:2626)
at
org.apache.wicket.MarkupContainer.onRender(MarkupContainer.java:1512)
at org.apache.wicket.Component.render(Component.java:2457)
at org.apache.wicket.MarkupContainer.autoAdd(MarkupContainer.java:229)
at
org.apache.wicket.markup.resolver.EnclosureResolver.resolve(EnclosureResolver.java:61)
at
org.apache.wicket.markup.resolver.ComponentResolvers.resolve(ComponentResolvers.java:81)
at
org.apache.wicket.MarkupContainer.renderNext(MarkupContainer.java:1418)
at
org.apache.wicket.MarkupContainer.renderAll(MarkupContainer.java:1528)
at org.apache.wicket.Page.onRender(Page.java:1545)
at org.apache.wicket.Component.render(Component.java:2457)
at org.apache.wicket.Page.renderPage(Page.java:914)
at
org.apache.wicket.request.target.component.BookmarkablePageRequestTarget.respond(BookmarkablePageRequestTarget.java:262)
at
org.apache.wicket.request.AbstractRequestCycleProcessor.respond(AbstractRequestCycleProcessor.java:105)
at
org.apache.wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:1258)
at org.apache.wicket.RequestCycle.step(RequestCycle.java:1329)
at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1428)
at org.apache.wicket.RequestCycle.request(RequestCycle.java:545)
at
org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:468)
at
org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:301)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1089)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365)
at
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712)
at
org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
at org.mortbay.jetty.Server.handle(Server.java:295)
at
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:503)
at
org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:827)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:511)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:210)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:379)
at
org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:226)
at
org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)
Re: taking the I out of Interface
+1 on removal of I Mostly because names and consistency are very important, not because I dislike I*. I also do not like Model (Locator is much better), but I understand the difficulties in this change - I think it would be even more confusing, when everything currently is related to "models" - wiki, docs, books :( But really, I think this should really be decided between the wicket commiters :). If this will make them love Wicket project even more (at put more hours in it :D ) - they can rename anything they want, I am willing to take whatever steps are required from my part to fix my existing code. Renaming staff is not that hard in modern ide. And so far upgrades from Wicket versions are S easy ... -- View this message in context: http://www.nabble.com/taking-the-I-out-of-Interface-tp25723691p25765194.html Sent from the Wicket - Dev mailing list archive at Nabble.com.
