A Wicket Diary

While perusing a series covering a business model based on the Amazon S3 software service I came across the following quote:

Outsiders do not realise how deeply technological development, like scientific research, is shaped and driven by emotion. [...] The reason that half of us are in computing at all is that we see computers as things that we can make beautiful things out of

And that really sums up my emotion when I am building creating software.

Matt Raible adds Wicket to the list of supported projects to the AppFuse Light project. Too bad he didn’t show which version is added (1.2.6 or the upcoming wicket 1.3.0).

The Wicket team is proud to announce another maintenance release for Wicket 1.2. With our first 1.3 release looming on the horizon, this probably marks the last 1.2 release. This release contains numerous fixes.

IMPORTANT NOTE

A critical bug has been identified in the request processing of Wicket. In rare cases this bug could lead to users being presented with a page from another user’s session. This bug is caused by a failure to clean up resources in the processing thread under very rare circumstances. See [WICKET-476] for more information on this issue.

Users are advised to upgrade their Wicket to 1.2.6. If you are using a custom built Wicket, please apply revision 529917 to your code.

Other issues

This release fixes other issues as well:

Bugs:

• [WICKET-9] - OnError does not work on file upload exceding max size
• [WICKET-134] - servlet.jar is included in the wicket examples war file.
• [WICKET-260] - Wicket uses trivial encryption if com.sun.crypto.provider.SunJCE is not available
• [WICKET-268] - NPE in ListView.renderItem(ListItem)
• [WICKET-269] - Calls to enabled and visibleInHierarchy should not be done in component resolving.
• [WICKET-276] - AbstractHeaderContributor.cleanup() will never be called
• [WICKET-281] - wicket-ajax.js is sometime missing from section
• [WICKET-290] - Inconsistent url generation
• [WICKET-291] - return immutable parameter map or a copy of parameters
• [WICKET-304] - AnnotSpringInjector corrupted class file in 1.2.5 release.
• [WICKET-342] - Application_sv.properties variable bugs
• [WICKET-349] - ListView can’t undo changes to model
• [WICKET-378] - autocomplete does not explicitly call input’s onchange event
• [WICKET-395] - Bookmarkable page problems
• [WICKET-432] - getvariation() is called from webpage constructor through commoninit()
• [WICKET-438] - File handles are leaked when loading images from a jar file, Tomcat crashes
• [WICKET-475] - NPE in WebClientInfo when user-agent header is not sent
• [WICKET-476] - Backport RequestCycle#updateSession and pagemap#session removal to 1.2.x
• [WICKET-490] - The wicket-auth-roles-1.2.5.jar contains the .svn subdirectories.

Improvement

• [WICKET-324] - AjaxFormComponentUpdatingBehavior updating other Component
• [WICKET-325] - Enable WebMarkupContainer as target for wicketSerialize

New Feature

• [WICKET-3] - listen for “selection changed” event at AutocompleteTextField
• [WICKET-338] - DateTextField

Although Wicket has recently entered the ASF Incubator, this interim release is provided outside of the ASF, solely as a service to existing Wicket users to resolve existing bugs in the Wicket product. As such, this release of the Wicket project is not endorsed or approved by the Apache Software Foundation. The Apache Software Foundation is in no way affiliated with this release.

• Download Wicket 1.2.6 here

I promised on the Wicket user list that I would devise a roadmap with some dates on when to expect releases. So here is a preliminary roadmap:

Some dates are not fixed, as there is an approval process to go through before we can ship it: the Apache releases tend to cause a bit more ceremony. When we have graduated you’ll see that these release procedures will become more efficient: there is no extra barrier to pass once we are a top level project. We have started the processes to release both Apache Wicket 1.3.0-incubating-beta and Wicket 1.2.6. The latter will be available this weekend, the former will be submitted to the Apache Incubator PMC for approval. We expect this release to become available around the end of the week after going back and forward a couple of times.

Note the release of wicket-x.y: we don’t know (yet) how to call the version after 1.3. The vote on the development list seems to favor Apache Wicket 2.0. This is a busy weekend for me: building 2 releases. Sounds like a great way to discover if we have improved on the release procedure in the last month.

We have now switched trunk and wicket 1.x in subversion. We have been getting reports of confused users about the status of Wicket and where to get the code from.

We appologize for the inconvenience this will cause.

From now on trunk is again our main development branch.

The previous Wicket 2 *with* constructor change has now been moved to branches/wicket-2-DISCONTINUED and is in maintenance mode (i.e. only bug fixes on a case-by-case basis).

Staying with Wicket 1.3

If you depended on branches/wicket-1.x do the following in your checked out working copy:

svn switch http://svn.apache.org/repos/asf/incubator/wicket/trunk

(if you are a Wicket committer, substitute http with https)

Staying with Wicket 2 *with* constructor change

If you were working on trunk and want to stay with the latest in that branch you will need to do the following in your working copy:

svn switch http://svn.apache.org/repos/asf/incubator/wicket/branches/wicket-2-DISCONTINUED

(if you are a Wicket committer, substitute http with https)

We will switch the svn branches in wicket-stuff too.