Repo for new site
Hi Martijn! I know your are super-busy with the Apache Con, but I wanted to ask you a question about the (possible) new site for Wicket. As you have seen this topic is getting much attention from other users and I would like to set up a sort of central repository to collect all contributes. So I want to ask you if you would like to make your repo (https://github.com/dashorst/wicket-site) as official or if you prefer a different solution. There is also the fork from Chris J. Lee who did a nice work to create a concrete flat them from your mocks. I could also decide to use my repo as official (https://github.com/bitstorm/wicket-site). I also forked Chris repo and I started to port the current contents to the new them. It looks very nice and very promising! I've completed the home page with news and the quickstart page (I think it's better to break a single page into different ones). News are already generated from _posts folder with Jekyll. You could see the final result here http://bitstorm.github.io/wicket-site/. I will prepare a readme file as well to explain the few conventions I've adopted. Let me know what do you think. Good luck and have tons of fun! Andrea.
IntHashMap is transient
Hi, https://issues.apache.org/jira/browse/WICKET-5751 and https://issues.apache.org/jira/browse/WICKET-5584 show a problem with the deserialization of IntHashMap https://github.com/apache/wicket/blob/master/wicket-util/src/main/java/org/apache/wicket/util/collections/IntHashMap.java . Many of its fields are transient for some reason and this leads to NullPointerExceptions when instances of IntHashMap are used after deserialization. Anyone have idea why these fields are transient ? Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov
Re: IntHashMap is transient
Hi Martin, I don't know why the fields are transient, Johan probably never expected the map to be serialized. Sven On 11/17/2014 04:57 PM, Martin Grigorov wrote: Hi, https://issues.apache.org/jira/browse/WICKET-5751 and https://issues.apache.org/jira/browse/WICKET-5584 show a problem with the deserialization of IntHashMap https://github.com/apache/wicket/blob/master/wicket-util/src/main/java/org/apache/wicket/util/collections/IntHashMap.java . Many of its fields are transient for some reason and this leads to NullPointerExceptions when instances of IntHashMap are used after deserialization. Anyone have idea why these fields are transient ? Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov
Re: IntHashMap is transient
I've noted this when I gave a quick look at WICKET-5751 but honestly I don't have any idea... Hi, https://issues.apache.org/jira/browse/WICKET-5751 and https://issues.apache.org/jira/browse/WICKET-5584 show a problem with the deserialization of IntHashMap https://github.com/apache/wicket/blob/master/wicket-util/src/main/java/org/apache/wicket/util/collections/IntHashMap.java . Many of its fields are transient for some reason and this leads to NullPointerExceptions when instances of IntHashMap are used after deserialization. Anyone have idea why these fields are transient ? Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov
Re: IntHashMap is transient
Ehh serialisation is done in read and writeobject methods, all the stuff should be created there (readObject) The entry array is not meant to be serialized by itself. At first sight it seem to be correct, the sizes are serialized and then an int + object pair is done. And the read creates the table and reads the pairs back in. Op 17 nov. 2014 20:20 schreef Sven Meier s...@meiers.net: Hi Martin, I don't know why the fields are transient, Johan probably never expected the map to be serialized. Sven On 11/17/2014 04:57 PM, Martin Grigorov wrote: Hi, https://issues.apache.org/jira/browse/WICKET-5751 and https://issues.apache.org/jira/browse/WICKET-5584 show a problem with the deserialization of IntHashMap https://github.com/apache/wicket/blob/master/wicket- util/src/main/java/org/apache/wicket/util/collections/IntHashMap.java . Many of its fields are transient for some reason and this leads to NullPointerExceptions when instances of IntHashMap are used after deserialization. Anyone have idea why these fields are transient ? Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov
Re: IntHashMap is transient
Oh, so obvious! Thanks, Johan ! Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Tue, Nov 18, 2014 at 1:29 AM, Johan Compagner jcompag...@gmail.com wrote: Ehh serialisation is done in read and writeobject methods, all the stuff should be created there (readObject) The entry array is not meant to be serialized by itself. At first sight it seem to be correct, the sizes are serialized and then an int + object pair is done. And the read creates the table and reads the pairs back in. Op 17 nov. 2014 20:20 schreef Sven Meier s...@meiers.net: Hi Martin, I don't know why the fields are transient, Johan probably never expected the map to be serialized. Sven On 11/17/2014 04:57 PM, Martin Grigorov wrote: Hi, https://issues.apache.org/jira/browse/WICKET-5751 and https://issues.apache.org/jira/browse/WICKET-5584 show a problem with the deserialization of IntHashMap https://github.com/apache/wicket/blob/master/wicket- util/src/main/java/org/apache/wicket/util/collections/IntHashMap.java . Many of its fields are transient for some reason and this leads to NullPointerExceptions when instances of IntHashMap are used after deserialization. Anyone have idea why these fields are transient ? Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov