Help wanted: test wicket 1.3 serialization

Eelco writes on the mailinglist after some (luke warm) discussion on how to test the new custom serialization Johan is building into the next Wicket versions. This is what he wrote:

Hi all,

We’re (Johan mostly) are experimenting with custom serialization to
see whether we could speed things up a bit (which doesn’t mean what we
have now is bad btw).

For anyone working on 1.3: we could use your help testing that
feature. The only thing you need to do is turn it on on your
development machine, by doing this in e.g. your application’s class
init method:

Objects.setObjectStreamFactory(new wicket.util.io.WicketObjectStreamFactory());

And then just report any issues you encounter to this list or the
developers list. Of course, if you have tweaks, test reports etc,
that’d be even cooler.

The default can be set like this:

Objects.setObjectStreamFactory(new IObjectStreamFactory.DefaultObjectStreamFactory());

which is based on JDK’s serialization. If you don’t configure
otherwise, that is what is used.

Thanks,

Eelco

So please help us out here and use the new WicketObjectStreamFactory in your development efforts and create bug reports if/when you find anything wrong.

The promise of this custom serialization is that it will improve the throughput and memory footprint of your Wicket application considerably. So help yourself, your employer and the Wicket community by testing the new serialization.

Oh no… another open source catalogue: Ohlo

Ohlo just surfaced on my radar. Ohlo is a open source catalogue, similar to the O’Reilly codezoo effort. We have Swik, Freshmeat, etc. How many of these efforts can the internet bear?

Ohlo does looks like a good effort. They parse the code repositories and base some of their statistics on that. A lot of sourceforge projects will fail the test as many will be flagged as one man, inactive projects.

Strange thing is that for the maven project (which is pretty heavy under development) they say that the activity is in decline. Probably the pointer to their repository was not correct.

Is such a catalogue any good? I think it is. I usually try to stay away from one man shows, and projects that haven’t seen much development (unless the software tracker shows no bugs and the project is feature complete). This catalogue shows in a blink of an eye the status of a project and adds nice qualities to it.

Their summary for Wicket:

+ Large, active development team
+ Well-commented source code
! Apache Software License may conflict with GPL

They flag the Apache Software License as conflicting with GPL. Apparently this is caused by one file in our repository trunk which is GPL licensed. The one problem I have is that they are able to discover one file with GPL code, but don’t provide a link to which file that is. Anyway, I doubt this will still be a problem in the next weeks. We are removing all (L)GPL code from our code base as our effort to incubate at Apache continues. The comments in our code seem to please the Ohlo gods:

Wicket is written mostly in Java. Across all Java projects on Ohloh, 35% of all source code lines are comments. For Wicket, this figure is 51%. This high number of comments puts Wicket among the highest one-third of all Java projects on Ohloh.

They conclude this factoid with the comment that the Wicket team is a [...] helpful and disciplined development team.

Read more on Wicket at Ohlo. Oh, and you can stack Wicket, which is something like telling that it is part of your software stack.

2007 Awards season opened

Yes! The Oscars are on its way, and Java developers can do their own voting for things important in your day to day job instead of some fantasy woman (such as Penélope Cruz). You can express your support for your favorite Java open source project at the following locations (and I know yours is Ruby on Rails Wicket)

Do I miss the JavaLobby and java.about.com yearly polls? Of course, TheServerSide.com has about a two-weekly polls where JSF gets trashed as being to complicated, Tapestry for being built up from start with every major release, Wicket for being to server memory hungry, Struts for being too old skool (or dead), RIFE for having ugly templates and so on. Perhaps they should create an award for the most uninteresting, uncriticized open source enterprise project.

What about the new comer: infoq, do they start a annual award soon? Or Hani Suleiman with an annual crap award (sort of the Razzies for Java software)?

I want to see some awards!