On 6/25/07, Seldon, Richard <[EMAIL PROTECTED]> wrote: > Really keen to know best place to get a list of outstanding defects between > releases wicket 1.2.4 and 1.2.6 is located? Are there release notes / URL > links etc with this info easily available? Apache issues list starts with > version 1.2.7 but this is no good in our case.
Click on the 'Releases' tab and you can see *all* releases. Then you have release notes for 1.2.5 and 1.2.6: * http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310561&styleName=Html&version=12312236 * http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310561&styleName=Html&version=12312305 > Our concurrency problem can be reproduced without load testing s/w and > (after exhaustively going through all our "static" code usages and other > possible areas of contention) likely explanation now sits with the version > of Wicket we're using. The Wicket website does include a section about a > critical bug in 1.2.4. In our case, if this is the problem, then it has > proven to be a show-stopper. Not knowing the details of your concurrency problem, I would urge anyone to upgrade to 1.2.6, because of the security implications of said bug. Now that you have it reproducable, could you provide a quickstart/other test so we can fix it? And before that, use 1.2.6 to see if that fixes your problem? > We are hoping to go live with our production release of SOA app in next few > days.... and have concluded we may need to either go with 1.2.6 (if the > migration is proven to fix our defects in test environments) or apply a > patch to 1.2.4 that covers just whats needed from 1.2.6 to fix the > cross-session issues. What is preventing you to upgrade to 1.2.6? > One other point I'd really like to hear discussion about:- we're using > WID version 2.0.1.2 which provides support for Java 1.4. At present, this > limits us up to Wicket 1.3 - will there be ongoing maintenance support for > users unable to migrate further due to limitations in the current app server > versions of Java support available? JDK 1.5 is already 2 years available. We have held off developing 1.5 features for long enough IMO. That said, we will support Wicket 1.3 for bug fixes, and possibly some features will be backported (portlet support may be one such feature), but that is based on available interest, and the impact of said feature on 1.3. Usually we shy away from API breaks, providing a binary compatible release on maintenance branches. And yes *eventually* we will stop support for 1.2 and 1.3 as technology progresses: this is a volunteer project and we only have limited time and resources. If you are anxious with respect to support for older versions, you might want to consider paid support. Wicket Support (http://wicket-support.com) will be happy to give you options. > As developers, we're definitely pro-Wicket but getting nervous regarding > this project's usage of Wicket and outstanding defects. Especially with > migration route options outlined above. I really don't understand what you are saying here. Martijn -- Wicket joins the Apache Software Foundation as Apache Wicket Join the wicket community at irc.freenode.net: ##wicket Wicket 1.2.6 contains a very important fix. Download Wicket now! http://wicketframework.org ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
