Thanks Martijn - great to hear!

Given your info, we are going to proceed with our own testing as well. We
will make sure to report back with any issues that we come across.

Thanks again,
Ben

-----Original Message-----
From: Martijn Dashorst [mailto:[email protected]]
Sent: Friday, April 23, 2010 4:38 AM
To: [email protected]
Subject: Re: Wicket 1.4 upgrade - dependent on Wicket Security 1.4

We're about to migrate our 800+ page application from 1.3.7 to 1.4.x
which heavily uses Wicket Security. So while the codebase for Wicket
Security 1.4 is already pretty stable we really want to ensure
everything works before we put a final/stable sticker on Wicket
Security 1.4.

Expect a Wicket Security 1.4-beta release in the next week or two and
a final release before the end of june (or possibly sooner).

Martijn


On Thu, Apr 22, 2010 at 10:02 PM, Ben Swenka <[email protected]>
wrote:
> Hello,
>
>
>
> We've been using Wicket 1.3.7 for quite a while now. We've been waiting
to
> upgrade to Wicket 1.4 until Wicket Security 1.4 was in a
released/production
> state.
>
>
>
> Can anybody provide any insight into the current state of Wicket
Security
> 1.4? Would you recommend upgrading with the Beta 1 code, or waiting
until
> Wicket Security 1.4 is in release/production mode?
>
>
>
> Is there a rough timeline on when Wicket Security 1.4 will be in a
> production/released status?
>
>
>
> Is anybody using Wicket 1.4/Wicket Security 1.4/Spring Security 2.0.x
> together in production?
>
>
>
> Thank you very much,
>
> Ben Swenka
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.4 increases type safety for web applications
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.4

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to