Our first public facing Wicket app went live today.
It's public facing and here it is- so I thought I'd blog about it.

As ever I was Technical Architect on this work and it was a technical pleasure.

It was our first wicket app - and it also uses Spring and Hibernate under the covers.

We ran a very agile process to go from a standing start to the finished product in the quickest possible time and I personally learned a lot about the strengths, and potential pitfalls, of a low calorie process :-)

If I get time I'll blog in a bit more technical depth on this app and the journey that we went on.

In the mean time hope things are good with any folk out their that read this.

Well I haven't blogged here for a while - and it's time to sort that out.
In the intervening years various things have happened.

• A large banking website that I did technical architecture on went live (hooray!)

• I've recently got into to Wicket as a UI framework and am overseeing architecture on two projects using it in the web tier (incidentally I attended a very good London Wicket User Group meeting the other day at Google's London offices)

• I've also been providing architectural consultancy for a number of well known organisations - which has been interesting. Seeing how other groups solve problems - sometimes in a way that I think is better than how I would have approached it and sometimes worse - has been a very interesting experience.

I've recently noticed that Wicket is becoming portlet friendly and am starting to investigate that:

• Resource 1
  
• Resource 2
  
• Resource 3
  
• Resource 4
  
  

Also apparently captcha is now easily read and broken by bot's this looks like a (very) cute replacement.....

Hope any readers that are out there are having a good year.....

Cheers