once 1.4 has been made final and has received it first or second
maintenance release. Then trunk will move to wicket 1.5, and 1.4 will
become our maintenance project.
Martijn
On Fri, Oct 17, 2008 at 12:59 PM, Martin Voigt [EMAIL PROTECTED] wrote:
Hi,
I'm currently building an ajax-heavy
Or maybe if the implementation is really rock solid, we *might*
introduce it into 1.4, but I wouldn't bet on it.
Martijn
On Fri, Oct 17, 2008 at 1:58 PM, Martijn Dashorst
[EMAIL PROTECTED] wrote:
once 1.4 has been made final and has received it first or second
maintenance release. Then trunk
Hi,
I'm currently building an ajax-heavy application and I'm using the new
implementation Matej is currently working on:
http://cwiki.apache.org/WICKET/wicket-15-ajax.html
I've noticed the *.ajaxng package is now *.ajax again in the
experimental repository
Whe ajaxng has package has been moved to _wicket package together with
some new requestcycle stuff (that is not integrated in wicket and
probably wont' be for quite some time).
I don't think ajaxng will make it to 1.4. It's not only about that
ajax implementation (that should be pretty stable),
Thanks for the responses.
I don't mind api changes at the current state of our project, I just
wanted to avoid doing a larger refactoring just before our release is
due. Since we're already using the wicket trunk for other apps I will
stay with ajaxng for the time beeing, as it's move to trunk is
