You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wicket.apache.org by Martijn Dashorst <ma...@gmail.com> on 2010/05/19 12:04:14 UTC
700+ page application switches from 1.3.7 to 1.4.8
Just two hours ago one of our developers pulled the trigger and
committed his Wicket 1.4.8 porting work for our flagship application
"EduArte" to our trunk. This means that as of this moment we finally
are near trunk and can start uncovering and fixing bugs for 1.4.x. We
expect to start work on porting our application towards 1.5 when we
have stabilized our 1.4.8 version.
A couple of statistics for our application:
- ~725 pages
- ~950 entities
- hibernate
- spring 3
- wicket security
- wiquery
The porting effort took a couple of months, tiered in 2 phases:
convert our framework (about a month), convert our application (about
a month).
Now the application needs to prove itself in testing and will probably
go live in a couple of weeks.
Martijn
Re: 700+ page application switches from 1.3.7 to 1.4.8
Posted by nino martinez wael <ni...@gmail.com>.
Sounds good, so do you expect that you'll find some bugs in "core"
wicket that the community will benefit from?
btw, just back from geecon where this speaker ,
Eugene Ciurana ( http://2010.geecon.org/speakerdetails/12 ) mentioned
(very discretely) wicket in conjunction with jboss as his preferred
stable stack.
2010/5/19 Martijn Dashorst <ma...@gmail.com>:
> Just two hours ago one of our developers pulled the trigger and
> committed his Wicket 1.4.8 porting work for our flagship application
> "EduArte" to our trunk. This means that as of this moment we finally
> are near trunk and can start uncovering and fixing bugs for 1.4.x. We
> expect to start work on porting our application towards 1.5 when we
> have stabilized our 1.4.8 version.
>
> A couple of statistics for our application:
> - ~725 pages
> - ~950 entities
> - hibernate
> - spring 3
> - wicket security
> - wiquery
>
> The porting effort took a couple of months, tiered in 2 phases:
> convert our framework (about a month), convert our application (about
> a month).
>
> Now the application needs to prove itself in testing and will probably
> go live in a couple of weeks.
>
> Martijn
>