| Subcribe via RSS or via Email

Updated terrcotta wicket-tim

December 7th, 2008 Posted in Java, Wicket

The latest version of the wicket 1.3 and terracotta integration is out (1.1.3).

The code will now automatically configure your application to use the correct page store, with a default of 100 pages history per page map.  If you need to override this value then you can override the the newSessionStore method in your WebApplication class, as in the previous version (see this post).

So in most cases all you need to do to use wicket with terracotta is include the tim in your terracotta configuration like so.

<module name="tim-wicket-1.3" version="1.1.3"/>

The next thing i’m going to be working on is wicket 1.4 support, which I should get finished before wicket 1.4 goes live.

7 Responses to “Updated terrcotta wicket-tim”

  1. Terracotta and Wicket (the next generation) | Richard Wilkinson's Blog Says:

    [...] with the 1.1.3 release you should follow the instructions on this post.  It is no longer required for you to set up the page store [...]


  2. Terracotta for Wicket (updated) | StuQ.nl Says:

    [...] his blog: The code will now automatically configure your application to use the correct page store, with a [...]


  3. erich oliphant Says:

    Any ETA on the Wicket 1.4 support? Any help needed ? :)


  4. Richard Says:

    I’m waiting for terracotta to support CopyOnWriteArray as 1.4 uses it internally (you can track progress here: http://jira.terracotta.org/jira/browse/CDV-1114)
    Once that is available it should hopefully be fairly simple to get working.
    If you are desperate then it would be possible to build your own wicket from source, replacing the offending classes with terracotta friendly ones.


  5. martin Says:

    Any update about this? 1.4-rc2 is not good enough?


  6. nino Says:

    It seems, http://jira.terracotta.org/jira/browse/CDV-1114 are closed so it should be upgradable now..


  7. Richard Says:

    Hi,

    Sorry about the slow reply, I must have missed the email.

    I saw that the issue had been updated, however I have not had time to change or test the tim. It is possible that it may just work as is now (maybe using some maven magic to exclude the old version of wicket). Failing that i’m sure they will accept patches / updates if someone else has time to take up this.

    Richard


Leave a Reply

retaggr