.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
View this message in context:
http://www.nabble.com/Stability-of-Wicket-1.4RC1-methods-interfaces%3A-new
My project team has decided we will go with Wicket to replace our aging
Struts 1.x infrastructure, so we're starting to learn to use Wicket in
earnest. The next question we face is whether to use Wicket 1.3 or
Wicket 1.4.
Since Wicket 1.4 is at RC1, and there is substantial use of generics
Betreff: Stability of Wicket 1.4RC1 methods/interfaces: new development on
1.3.5 or 1.4RC1?
My project team has decided we will go with Wicket to replace our aging
Struts 1.x infrastructure, so we're starting to learn to use Wicket in
earnest. The next question we face is whether to use Wicket 1.3
1.4-rc1 is safe to go with (my opinion - i have quite a few apps currently
deployed on various versions of 1.4 (m2 / m3 / and now rc1).
You go on to describe problems with differences between 1.3 / 1.4 - what
errors are you specifically seeing? I think everything is pretty well
documented, but
Jeremy Thomerson wrote:
1.4-rc1 is safe to go with (my opinion - i have quite a few apps currently
deployed on various versions of 1.4 (m2 / m3 / and now rc1).
So long as the interfaces are NOT likely to make major changes (where
major = along the lines of the getModel - getDefaultModel
The API is pretty locked for now - only a significant bug found would cause
a change. A significant bug is fairly unlikely considering that so many
people are running production apps against it already and the changes from
1.3 - 1.4 were not many (functionally).
I don't know about a date for 1.4
