I only wish we could get as many to attend as they have in The Netherlands. At this writing there are 68! attending. What is happening in NL?
UPDATE: Now there are 82 attendees!! Martijn also asked me if I wanted to come by, but I can’t make it this time. Maybe next time.
In this announcement:
Eager people click here to download the distribution, others can read further:
http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta4/
We thank you for your patience and support. Given the current list of remaining issues and the fact that we have just accepted portlet support back in, we think a fifth beta release is necessary. But that is no excuse for not giving this fourth installment a test drive!
The Wicket Team
Apache Wicket is a component oriented Java web application framework currently undergoing incubation at the Apache Software foundation. With proper mark-up/logic separation, a POJO data model, and a refreshing lack of XML, Apache Wicket makes developing web-apps simple and enjoyable again. Swap the boilerplate, complex debugging and brittle code for powerful, reusable components written with plain Java and HTML.
Our migration to a top level project is now completed and you can find our website and documentation here:
This release is the fourth in a series of beta releases until we feel confident to finalize Wicket 1.3. This is called a beta because we don’t have fixed all bugs, and probably haven’t found them all either.
A new feature in this beta4 release is the merge of Ate Douma’s portlet branch into trunk. This reintroduces portlet support in Wicket.
http://cwiki.apache.org/WICKET/portal-howto.html
If you are coming from Wicket 1.2, you really want to read our migration guide, found on the wiki:
http://cwiki.apache.org/WICKET/migrate-13.html
You can download the release from the official Apache mirror system, and you can find it through the following link:
http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta4/
For the Maven and Ivy fans out there: update your pom’s to the following, and everything will be downloaded automatically:
<dependency>
<groupId>org.apache.wicket</groupId>
<artifactId>wicket</artifactId>
<version>1.3.0-beta4</version>
</dependency>
Substitute the artifact ID with the projects of your liking to get the other projects.
Please note that we don’t prescribe a Logging implementation for SLF4J. You need to specify yourself which one you prefer. Read more about SLF4J here: http://slf4j.org
The release has been signed by Frank Bille, your release manager for today. The public key can be found in the KEYS file in the download area. Download the KEYS file only from the Apache website.
http://www.apache.org/dist/wicket/1.3.0-beta4/KEYS
Instructions on how to validate the release can be found here:
http://www.apache.org/dev/release-signing.html#check-integrity
In case you do encounter a bug, we would appreciate a report in our JIRA:
http://issues.apache.org/jira/browse/WICKET
In the distribution you will find a README. The README contains instructions on how to build from source yourself and a list of all things that have been fixed, added and/or removed since the first beta release.
Wicket has graduated from Apache Incubator and has now become an Apache top level project. I would like to thank all the guys who made this possible and especially Martijn (our new PMC Chair). I’m trying to plan a little get-together/meeting in Copenhagen where we would also get a change to drink a glass of Champagne to celebrate it. Join us if you live near Copenhagen!
Wicket is a Java web application framework that takes simplicity, separation of concerns and ease of development to a whole new level. Wicket pages can be mocked up, previewed and later revised using standard WYSIWYG HTML design tools. Dynamic content processing and form handling is all handled in Java code using a first-class component model backed by POJO data beans that can easily be persisted using your favorite technology.
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. Fixed bugs in Wicket 1.2.4
The wicket-team is pleased to announce the release of Wicket 1.2.3! This is a bug fix release for Wicket and is the last release for the 1.2 branch, which now enters maintainance mode. We will now focus on Wicket 2.0 and 1.3.
Even though it is a bug fix release some new features has also sneaked in. F.ex. JMX support, which in 1.2 is in a different project but in 2.0 will be integrated in core.
Oh, and by the way. Martijn has created a special Halloween look for the wicket website. Check it out 
(For those reading this long after halloween 2006 take a look at the screenshot below):
The [Wicket project][wicket] has released the first maintainance release for Wicket 1.2. This is the first release which has some of my patches in it. This has mostly to do with extending the WicketTester to support testing of AJAX enabled applications. But I have also done a RfcCompliantEmailValidator for wicket-extensions, which validates emails according to the RFC.
Other noticeable highlights (taken from the [Release Notes][release]:
* For improved reliability, instead of utilizing cookies and falling back on a quirky JavasScript, we now use window.name to detect whether we are in sync with the proper page map.
* AjaxFormSubmitBehavior no longer incorrectly calls onSubmit() if an error occured during form processing (this aligns it with Button.onSubmit() semantic), instead a new onError() method will be called to allow for error related ajax target processing.
[wicket]: http://www.wicketframework.org/
[release]: http://sourceforge.net/forum/forum.php?forum_id=594030
Since [trunk][trunk] went 2.0 there have been an extensive amount of failing unit tests. Many of them is because Wicket 2.0 is going to handle things differently which means some of the tests needs to be rewritten/changed to match the new behaviors. These are actually the hardest tests to fix, because they require some knowhow of the specific test.
Some of the tests fails because the ordering of the attributes when added to a tag from Wicket has changed. So all the diff tests which compares the output generated with a static html file now fails. The solution here is quite simple: Just create new static html files for comparison.
Last there were some tests that failed because you can’t add components to parent, which isn’t backed in a Markup file. Many tests just used a dummy page, with no .html file and therefore no matching wicket:id’s for the components added to that page. The solution for this is to have html files which matches the component tree in the tests. Luckily many of the tests had the exact same component hierachy (namely a Page with one component on it), so it didn’t require a new .html file for every one of them.
Yesterday I [fixed][patch] all the failing tests of the last type. I just hate failing unit tests 
[trunk]: http://svn.sourceforge.net/viewcvs.cgi/wicket/trunk/
[patch]: http://svn.sourceforge.net/viewcvs.cgi/wicket?rev=6274&view=rev
I have begun extending the WicketTester to ease the testing of AJAX enabled Wicket applications
My first [patch][revision] extends the clickLink method into accepting clicks on
an AjaxLink. The method then invokes the onClick method on the AjaxLink.
This is a good way to simulate that a user clicks on an AjaxLink. At [Avaleo][avaleo] we use this
method a lot when testing that the flow is correct etc.
The next patch is going to be about actually testing that a component is added to an AjaxRequestTarget
when an AjaxEvent is fired. More on that later…
[revision]: http://svn.sourceforge.net/viewcvs.cgi/wicket?rev=6254&view=rev
[avaleo]: http://www.avaleo.net/
I have added a [patch][revision] for [Wicket 2.0][trunk] which introduces a [ClientEvent enum][clientevent]
for specifying which event on the client should fire the event.
So where you in 1.2 would write something like this:
...
Label label = new Label("label", "This is my label");
label.add(new AjaxEventBehavior("onclick") {
public void onEvent(AjaxRequestTarget target) {
// Do your stuff here.
}
});
...
You now write this:
...
Label lavel = new Label(parent, "label", "This is my label");
label.add(new AjaxEventBehavior(ClientEvent.CLICK) {
public void onEvent(AjaxRequestTarget target) {
// Do your stuff here.
}
});
Which eliminates the problem with misspelling the event name (like “onclck”, “click” or “onclicked”).
[revision]: http://svn.sourceforge.net/viewcvs.cgi/wicket?rev=6243&view=rev
[trunk]: http://svn.sourceforge.net/viewcvs.cgi/wicket/trunk/wicket/
[clientevent]: http://svn.sourceforge.net/viewcvs.cgi/wicket/trunk/wicket/src/java/wicket/ajax/ClientEvent.java?view=markup
The [Wicket development team][wicket] has released the next major release of Wicket.
They have put a lot of effort into making it even more easy for us to develop
professional webapplications. Some of the new features which I think is particulary
useful is the new [AJAX][ajax] support and the WicketTester. (Read the full
[release note][release])
The WicketTester is a great way to test your components without having to use a
container for it. At [Avaleo][avaleo], we have used this the last couple of month since
some of the first beta releases of 1.2 and it really speeds up writing unit tests
for all the components, pages etc that we create.
The last month I have played around with the [AJAX][ajax] implementation and I most say that
it really is nice that you don’t have to do any Javascript yourself to make it work.
At the moment we are strongly considering using [AJAX][ajax] in our application so it’s
great that Wicket provides such a clean and simple API for it.
Just to mention some of the other new features which I believe makes a difference (at least
for me at the moment):
Taken from the [release note][release]:
* Nice URL support through URL mounting
* Spring support for injecting your business logic into your web pages in a non-intrusive manner, while still being able to use the convenient Wicket idiom for creating pages (using the Java new operator).
* Improved performance by replacing OGNL with our own object graph language parser
[wicket]: http://www.wicketframework.org
[ajax]: http://en.wikipedia.org/wiki/Ajax_%28programming%29
[avaleo]: http://www.avaleo.net/
[release]: http://sourceforge.net/mailarchive/forum.php?thread_id=10467093&forum_id=46143
