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 2008/01/01 23:05:37 UTC

[discuss] Wicket 1.3 release notes

h1. Apache Wicket 1.3 released The Wicket team wishes everybody a happy new
year and starts 2008 promising with a fresh new release: Apache Wicket 1.3.
"Apache Wicket":http://wicket.apache.org is a Java open source component
based web application framework. Apache Wicket was established as a top
level project at the Apache Software Foundation on June 20th 2007. With
proper mark-up/logic separation, a POJO data model, and a refreshing lack of
XML, Apache Wicket makes developing web-apps simple and enjoyable again.
Swap the boilerplate, complex debugging and brittle code for powerful,
reusable components written with plain Java and HTML. This new release
features some considerable improvements over previous releases and
stabilizes several core API's. Highlights from this release: * last
JDK-1.4release (next release will be Java 5 based) * package move from
@wicket@ to
@org.apache.wicket@ -- Wicket joined the Apache Software foundation and
renaming all packages to go into the Apache namespace reflects this move *
simplified models API -- the number of Model classes was minimized, the
@Component@ parameter to the @get/setObject@ methods has been removed as it
was not always clear which component to provide * simplified converter API
-- converters now need two methods (see interface @IConverter@):
@convertToObject(String, Locale)@ and @convertToString(Object, Locale)@,
this makes rolling your own custom converters much easier * all URL's are
now generated as relative URL's -- this means it works with zero-config
behind a proxy server * simplified validator API -- the validator API has
been decoupled from Wicket's form component hierarchy allowing you to create
validators so that validators can be reused outside Wicket * guice support
-- want to use Google's guice as your dependency injection framework?
wicket-guice makes it easy: @@Inject private IService service;@ will inject
the IService implementation into your Wicket component. * portlet support
("JSR-168":http://jcp.org/en/jsr/detail?id=168, "JSR-286":
http://jcp.org/en/jsr/detail?id=286) -- Wicket pages can now work directly
in a portal as portlets without changing a line of code (no separate
component hierarchy), learn more about Wicket's portlet support in this
presentation by Ate Douma: "Wicket portlet primer":
http://www.slideshare.net/ate.douma/wicket-portlet-primer * switched logging
API from commons-logging to slf4j * improved Ajax support -- new Ajax
components can be added to the page and contribute new javascript
dependencies to the page header, hide/show components using Ajax without
workarounds (@setOutputMarkupPlaceHolderTag@) * added @<wicket:enclosure>@
and @<wicket:container>@ tags -- @<wicket:enclosure>@ is a grouping tag for
controlling visibility of markup surrounding a component,
@<wicket:container>@ can add components' markup in places where it would
make the page non-w3c compliant * stateless pages and components for those
parts of your application that needs to scale * hybrid URL encoding to make
search engines and your users happy (see "Thoof":http://thoof.com for an
example in action) * nested form components -- create panels that contain
forms and use them anywhere without having to worry about the nesting of
forms * minimized session use by storing component hierarchy in file system
(DiskPageStore) And much more small updates, upgrades and new features. As
there have been API breaks you will need to do some work on your existing
applications to make it 1.3 compliant. This is not a drop-in replacement for
Wicket 1.2. The release is accompanied with a "migration guide":
http://cwiki.apache.org/WICKET/migrate-13.html and "live examples":
http://wicketstuff.org/wicket13 (the examples are part of the distribution).
The distribution contains the Wicket jars and all sources. You can download
the release here on one of the "Apache mirrors":
http://www.apache.org/dyn/closer.cgi/wicket/1.3.0 While we take a break
recuperating from the holidays, we have begun planning the next version: it
will be Java 5 based, introduce generics into the models, and some other
"nice stuff":http://cwiki.apache.org/WICKET/wicket-14-wish-list.html. You
can help and discuss the future of Wicket on our mailing list.

Re: [discuss] Wicket 1.3 release notes

Posted by Martijn Dashorst <ma...@gmail.com>.
With the help of Christopher Bergström (codest0m iirc on ##wicket) we came
up with:
Starting the new year with a bang the Wicket Team has released Apache Wicket
1.3. With this release comes a lot of great successes, but most of all the
team wanted to express their wishes to everyone for a happy new year. <a
href="http://wicket.apache.org">Apache Wicket</a> is one of the fastest
growing Java open source component based web frameworks. With a focus on
producing valid html and a logical separation between design and code.
Within minutes you can start to enjoy throwing out tag soup, complex
components and high maintenance overhead for a simple POJO + html data
model. Take a look at some of the following highlights or skip to the bottom
and get started now. <ul> <li>last JDK-1.4 release (next release will be
Java 5 based)</li> <li>first Apache release: renamed packages to <code>
org.apache.wicket</code></li> <li>simplified several core APIs</li> <li>now
works with zero-config behind a proxy server using relative URLs</li>
<li>added Google Guice support</li> <li>use your Wicket pages directly in a
portal without changing a line of code (JSR-168/JSR-286 support)</li>
<li>switched logging API from commons-logging to slf4j</li> <li>integrate
velocity templates as panels in your pages</li> <li>YUI-calendar and Joda
time based date picker (wicket-datetime)</li> <li>contribute new javascript
dependencies to the page header using an Ajax requeset</li> <li>improved,
more robust header contributions: filter duplicate javascript references,
support onload/ondomready event support, and compress javascript resources
by default</li> <li>scale to extremely large numbers of users with stateless
pages and components</li> <li>improved AjaxTree/AjaxTreeTable</li>
<li>hybrid URL encoding to make search engines and your users happy</li>
<li>create form panels and use them anywhere without worrying about the
nesting of form tags</li> <li>minimized session use by storing component
hierarchy in file system (DiskPageStore)</li> </ul> Get started today by
checking out the following examples or follow the download link directly at
the bottom. <ul> <li><a href="
http://wicketstuff.org/wicket13/repeater/?wicket:bookmarkablePage=%3Aorg.apache.wicket.examples.repeater.AjaxDataTablePage">Basic
Ajax Repeater with paging</a></li> <li><a href="
http://wicketstuff.org/wicket13">Fundamental components</a></li> <li><a
href="http://www.apache.org/dyn/closer.cgi/wicket/1.3.0">Download Apache
Wicket 1.3</a></li> </ul> Best wishes from the Wicket Team and a prosperous
2008!

Re: [discuss] Wicket 1.3 release notes

Posted by Martijn Dashorst <ma...@gmail.com>.
On 1/2/08, Frank Bille <fr...@apache.org> wrote:
>
> But perhaps you should wait until ~23.00+2 so all mirrors has had a chance
> to pick it up?



I'd rather post it myself than have others do it before me, which is going
to happen shortly as folks are anxious to get it out. Either way it is going
to be published before 23:00, whether we like it or not....

Martijn


-- 
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.0-rc2 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-rc1/

Re: [discuss] Wicket 1.3 release notes

Posted by Frank Bille <fr...@apache.org>.
I don't have anything that hasn't been said elsewhere.

But perhaps you should wait until ~23.00+2 so all mirrors has had a chance
to pick it up?

Frank


On Jan 2, 2008 3:47 PM, Martijn Dashorst <ma...@gmail.com> wrote:

> If there aren't any further comments (within an hour or so), I'll release
> this as the announcement for 1.3.
> Martijn
>
>
> On Jan 1, 2008 11:28 PM, Martijn Dashorst <ma...@gmail.com>
> wrote:
>
> > Apache Wicket 1.3 released
> >
> > The Wicket team wishes everybody a happy new year and starts 2008
> > promising with a fresh new release: Apache Wicket 1.3.
> >
> > Apache Wicket <http://wicket.apache.org/> is a Java open source
> component
> > based web application framework. Apache Wicket was established as a top
> > level project at the Apache Software Foundation on June 20th 2007. With
> > proper mark-up/logic separation, a  POJO data model, and a refreshing
> lack
> > of XML, Apache Wicket makes developing web-apps simple and enjoyable
> > again. Swap the boilerplate, complex debugging and brittle code for
> > powerful, reusable components written with plain Java and  HTML.
> >
> > This new release features some considerable improvements over previous
> > releases and stabilizes several coreAPI's. Highlights from this release:
> >
> >    - last  JDK-1.4 release (next release will be Java 5 based)
> >    - package move from wicket to  org.apache.wicket—Wicket joined the
> >    Apache Software foundation and renaming all packages to go into the
> Apache
> >    namespace reflects this move
> >    - simplified models API—the number of Model classes was minimized,
> >    the Component  parameter to theget/setObject methods has been
> >    removed as it was not always clear which component to provide
> >    - simplified converter API—converters now need two methods (see
> >    interface IConverter ):convertToObject(String, Locale) and
> convertToString(Object, Locale),
> >    this makes rolling your own custom converters much easier
> >    - all URL's are now generated as relative URL's—this means it works
> >    with zero-config behind a proxy server
> >    - simplified validator API—the validator API has been decoupled from
> >    Wicket's form component hierarchy allowing you to create validators
> so that
> >    validators can be reused outside Wicket
> >    - guice support—want to use Google's guice as your dependency
> >    injection framework? wicket-guice makes it easy: @Inject private
> >    IService service;  will inject the IService implementation into your
> >    Wicket component.
> >    - portlet support (JSR-168 <http://jcp.org/en/jsr/detail?id=168>,
> >    JSR-286 <http://jcp.org/en/jsr/detail?id=286>)—Wicket pages can now
> >    work directly in a portal as portlets without changing a line of code
> (no
> >    separate component hierarchy), learn more about Wicket's portlet
> support in
> >    this presentation by Ate Douma:  Wicket portlet primer<
> http://www.slideshare.net/ate.douma/wicket-portlet-primer>
> >    - switched logging API from commons-logging to slf4j
> >    - Velocity panel—project wicket-velocity allows you to integrate
> >    velocity templates as panels in your pages
> >    - YUI-calendar <http://developer.yahoo.com/yui/calendar//> time":
> >    http://joda-time.sourceforge.net/ based date picker
> >    (wicket-datetime)
> >    - improved Ajax support—new Ajax components can be added to the page
> >    and contribute new javascript dependencies to the page header,
> hide/show
> >    components using Ajax without workarounds
> (setOutputMarkupPlaceHolderTag
> >    )
> >    - added <wicket:enclosure> and  <wicket:container> tags—
> >    <wicket:enclosure> is a grouping tag for controlling visibility of
> >    markup surrounding a component,  <wicket:container> can add
> >    components' markup in places where it would make the page non-w3c
> compliant
> >    - stateless pages and components for those parts of your application
> >    that needs to scale
> >    - hybrid URL encoding to make search engines and your users happy
> >    (see  Thoof <http://thoof.com/> for an example in action)
> >    - nested form components—create panels that contain forms and use
> >    them anywhere without having to worry about the nesting of forms
> >    - minimized session use by storing component hierarchy in file
> >    system (DiskPageStore)
> >
> > And much more small updates, bug fixes, upgrades and new features. As
> > there have been API breaks you will need to do some work on your
> existing
> > applications to make it 1.3 compliant. This is not a drop-in replacement
> > for Wicket 1.2. The release is accompanied with a migration guide<
> http://cwiki.apache.org/WICKET/migrate-13.html>
> > .
> >
> > You can see Wicket in action with our live examples<
> http://wicketstuff.org/wicket13> The
> > distribution contains the Wicket jars and all sources, including the
> > examples. You can download the release on one of the  Apache mirrors<
> http://www.apache.org/dyn/closer.cgi/wicket/1.3.0>
> >
> > While we take a break recuperating from the holidays, we have begun
> > planning the next version: it will be Java 5 based, introduce generics
> into
> > the models, and some other  nice stuff<
> http://cwiki.apache.org/WICKET/wicket-14-wish-list.html>.
> > You can help and discuss the future of Wicket on our mailing list.
> >
>
>
>
> --
> Buy Wicket in Action: http://manning.com/dashorst
> Apache Wicket 1.3.0-rc2 is released
> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-rc1/
>

Re: [discuss] Wicket 1.3 release notes

Posted by Martijn Dashorst <ma...@gmail.com>.
If there aren't any further comments (within an hour or so), I'll release
this as the announcement for 1.3.
Martijn


On Jan 1, 2008 11:28 PM, Martijn Dashorst <ma...@gmail.com>
wrote:

> Apache Wicket 1.3 released
>
> The Wicket team wishes everybody a happy new year and starts 2008
> promising with a fresh new release: Apache Wicket 1.3.
>
> Apache Wicket <http://wicket.apache.org/> is a Java open source component
> based web application framework. Apache Wicket was established as a top
> level project at the Apache Software Foundation on June 20th 2007. With
> proper mark-up/logic separation, a  POJO data model, and a refreshing lack
> of XML, Apache Wicket makes developing web-apps simple and enjoyable
> again. Swap the boilerplate, complex debugging and brittle code for
> powerful, reusable components written with plain Java and  HTML.
>
> This new release features some considerable improvements over previous
> releases and stabilizes several coreAPI's. Highlights from this release:
>
>    - last  JDK-1.4 release (next release will be Java 5 based)
>    - package move from wicket to  org.apache.wicket—Wicket joined the
>    Apache Software foundation and renaming all packages to go into the Apache
>    namespace reflects this move
>    - simplified models API—the number of Model classes was minimized,
>    the Component  parameter to theget/setObject methods has been
>    removed as it was not always clear which component to provide
>    - simplified converter API—converters now need two methods (see
>    interface IConverter ):convertToObject(String, Locale) and convertToString(Object, Locale),
>    this makes rolling your own custom converters much easier
>    - all URL's are now generated as relative URL's—this means it works
>    with zero-config behind a proxy server
>    - simplified validator API—the validator API has been decoupled from
>    Wicket's form component hierarchy allowing you to create validators so that
>    validators can be reused outside Wicket
>    - guice support—want to use Google's guice as your dependency
>    injection framework? wicket-guice makes it easy: @Inject private
>    IService service;  will inject the IService implementation into your
>    Wicket component.
>    - portlet support (JSR-168 <http://jcp.org/en/jsr/detail?id=168>,
>    JSR-286 <http://jcp.org/en/jsr/detail?id=286>)—Wicket pages can now
>    work directly in a portal as portlets without changing a line of code (no
>    separate component hierarchy), learn more about Wicket's portlet support in
>    this presentation by Ate Douma:  Wicket portlet primer<http://www.slideshare.net/ate.douma/wicket-portlet-primer>
>    - switched logging API from commons-logging to slf4j
>    - Velocity panel—project wicket-velocity allows you to integrate
>    velocity templates as panels in your pages
>    - YUI-calendar <http://developer.yahoo.com/yui/calendar//> time":
>    http://joda-time.sourceforge.net/ based date picker
>    (wicket-datetime)
>    - improved Ajax support—new Ajax components can be added to the page
>    and contribute new javascript dependencies to the page header, hide/show
>    components using Ajax without workarounds (setOutputMarkupPlaceHolderTag
>    )
>    - added <wicket:enclosure> and  <wicket:container> tags—
>    <wicket:enclosure> is a grouping tag for controlling visibility of
>    markup surrounding a component,  <wicket:container> can add
>    components' markup in places where it would make the page non-w3c compliant
>    - stateless pages and components for those parts of your application
>    that needs to scale
>    - hybrid URL encoding to make search engines and your users happy
>    (see  Thoof <http://thoof.com/> for an example in action)
>    - nested form components—create panels that contain forms and use
>    them anywhere without having to worry about the nesting of forms
>    - minimized session use by storing component hierarchy in file
>    system (DiskPageStore)
>
> And much more small updates, bug fixes, upgrades and new features. As
> there have been API breaks you will need to do some work on your existing
> applications to make it 1.3 compliant. This is not a drop-in replacement
> for Wicket 1.2. The release is accompanied with a migration guide<http://cwiki.apache.org/WICKET/migrate-13.html>
> .
>
> You can see Wicket in action with our live examples<http://wicketstuff.org/wicket13> The
> distribution contains the Wicket jars and all sources, including the
> examples. You can download the release on one of the  Apache mirrors<http://www.apache.org/dyn/closer.cgi/wicket/1.3.0>
>
> While we take a break recuperating from the holidays, we have begun
> planning the next version: it will be Java 5 based, introduce generics into
> the models, and some other  nice stuff<http://cwiki.apache.org/WICKET/wicket-14-wish-list.html>.
> You can help and discuss the future of Wicket on our mailing list.
>



-- 
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.0-rc2 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-rc1/

Re: [discuss] Wicket 1.3 release notes

Posted by Martijn Dashorst <ma...@gmail.com>.
thx!
Fixing as we speak. (the missing space is due to the HTML conversion,
nothing I did wrong :)

Martijn

On Jan 2, 2008 4:08 PM, David Shepherdson <
david.shepherdson@ontology-partners.com> wrote:

> Just a few grammatical/typo things:
>
> On 1 Jan 2008, at 10.28 pm, Martijn Dashorst wrote:
>
> > Apache Wicket 1.3 released
> >
> > The Wicket team wishes everybody a happy new year and starts 2008
> > promising
>
> Maybe that should be 'promisingly'?
>
> ...
>
> > This new release features some considerable improvements over previous
> > releases and stabilizes several coreAPI's. Highlights from this
> > release:
>
> Missing space after 'core'. I would say you don't need an apostrophe
> for 'APIs' (but I realise there is some debate around that... :-)).
>
> ...
>
> >   - simplified models API—the number of Model classes was minimized,
> >   the Component parameter to theget/setObject methods has been removed
>
> Missing space after 'the'.
>
> ...
>
> >   - all URL's are now generated as relative URL's—this means it works
>
> Again, the apostrophes shouldn't be needed on 'URLs'.
>
> ...
>
> >   - simplified validator API—the validator API has been decoupled from
> >   Wicket's form component hierarchy allowing you to create
> > validators so that
> >   validators can be reused outside Wicket
>
> Maybe just '...create validators that can be reused outside WIcket'?
>
> ...
>
> >   markup surrounding a component, <wicket:container> can add
> > components'
> >   markup in places where it would make the page non-w3c compliant
>
> Maybe capitals for 'W3C'?
>
> ...
>
> >   - stateless pages and components for those parts of your application
> >   that needs to scale
>
> Should be 'need' (singular).
>
> ...
>
> > And much more small updates, bug fixes, upgrades and new features.
> > As there
>
> Should be 'And many more...'.
>
> ...
>
> > have been API breaks you will need to do some work on your existing
> > applications to make it 1.3 compliant. This is not a drop-in
> > replacement for
>
> Should be '...to make them 1.3 compliant.'
>
> Hope this helps!
>
> David




-- 
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.0-rc2 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-rc1/

Re: [discuss] Wicket 1.3 release notes

Posted by David Shepherdson <da...@ontology-partners.com>.
Just a few grammatical/typo things:

On 1 Jan 2008, at 10.28 pm, Martijn Dashorst wrote:

> Apache Wicket 1.3 released
>
> The Wicket team wishes everybody a happy new year and starts 2008  
> promising

Maybe that should be 'promisingly'?

...

> This new release features some considerable improvements over previous
> releases and stabilizes several coreAPI's. Highlights from this  
> release:

Missing space after 'core'. I would say you don't need an apostrophe  
for 'APIs' (but I realise there is some debate around that... :-)).

...

>   - simplified models API—the number of Model classes was minimized,
>   the Component parameter to theget/setObject methods has been removed

Missing space after 'the'.

...

>   - all URL's are now generated as relative URL's—this means it works

Again, the apostrophes shouldn't be needed on 'URLs'.

...

>   - simplified validator API—the validator API has been decoupled from
>   Wicket's form component hierarchy allowing you to create  
> validators so that
>   validators can be reused outside Wicket

Maybe just '...create validators that can be reused outside WIcket'?

...

>   markup surrounding a component, <wicket:container> can add  
> components'
>   markup in places where it would make the page non-w3c compliant

Maybe capitals for 'W3C'?

...

>   - stateless pages and components for those parts of your application
>   that needs to scale

Should be 'need' (singular).

...

> And much more small updates, bug fixes, upgrades and new features.  
> As there

Should be 'And many more...'.

...

> have been API breaks you will need to do some work on your existing
> applications to make it 1.3 compliant. This is not a drop-in  
> replacement for

Should be '...to make them 1.3 compliant.'

Hope this helps!

David

Re: [discuss] Wicket 1.3 release notes

Posted by Martijn Dashorst <ma...@gmail.com>.
Apache Wicket 1.3 released

The Wicket team wishes everybody a happy new year and starts 2008 promising
with a fresh new release: Apache Wicket 1.3.

Apache Wicket <http://wicket.apache.org/> is a Java open source component
based web application framework. Apache Wicket was established as a top
level project at the Apache Software Foundation on June 20th 2007. With
proper mark-up/logic separation, a POJO data model, and a refreshing lack
of XML, Apache Wicket makes developing web-apps simple and enjoyable again.
Swap the boilerplate, complex debugging and brittle code for powerful,
reusable components written with plain Java and HTML.

This new release features some considerable improvements over previous
releases and stabilizes several coreAPI's. Highlights from this release:

   - last JDK-1.4 release (next release will be Java 5 based)
   - package move from wicket to org.apache.wicket—Wicket joined the
   Apache Software foundation and renaming all packages to go into the Apache
   namespace reflects this move
   - simplified models API—the number of Model classes was minimized,
   the Component parameter to theget/setObject methods has been removed
   as it was not always clear which component to provide
   - simplified converter API—converters now need two methods (see
   interface IConverter):convertToObject(String, Locale) and
convertToString(Object,
   Locale), this makes rolling your own custom converters much easier
   - all URL's are now generated as relative URL's—this means it works
   with zero-config behind a proxy server
   - simplified validator API—the validator API has been decoupled from
   Wicket's form component hierarchy allowing you to create validators so that
   validators can be reused outside Wicket
   - guice support—want to use Google's guice as your dependency
   injection framework? wicket-guice makes it easy: @Inject private
   IService service; will inject the IService implementation into your
   Wicket component.
   - portlet support (JSR-168 <http://jcp.org/en/jsr/detail?id=168>, JSR
   -286 <http://jcp.org/en/jsr/detail?id=286>)—Wicket pages can now work
   directly in a portal as portlets without changing a line of code (no
   separate component hierarchy), learn more about Wicket's portlet support in
   this presentation by Ate Douma: Wicket portlet
primer<http://www.slideshare.net/ate.douma/wicket-portlet-primer>
   - switched logging API from commons-logging to slf4j
   - Velocity panel—project wicket-velocity allows you to integrate
   velocity templates as panels in your pages
   - YUI-calendar <http://developer.yahoo.com/yui/calendar//> time":
   http://joda-time.sourceforge.net/ based date picker (wicket-datetime)
   - improved Ajax support—new Ajax components can be added to the page
   and contribute new javascript dependencies to the page header, hide/show
   components using Ajax without workarounds (
   setOutputMarkupPlaceHolderTag)
   - added <wicket:enclosure> and <wicket:container> tags—
   <wicket:enclosure> is a grouping tag for controlling visibility of
   markup surrounding a component, <wicket:container> can add components'
   markup in places where it would make the page non-w3c compliant
   - stateless pages and components for those parts of your application
   that needs to scale
   - hybrid URL encoding to make search engines and your users happy
   (see Thoof <http://thoof.com/> for an example in action)
   - nested form components—create panels that contain forms and use them
   anywhere without having to worry about the nesting of forms
   - minimized session use by storing component hierarchy in file system
   (DiskPageStore)

And much more small updates, bug fixes, upgrades and new features. As there
have been API breaks you will need to do some work on your existing
applications to make it 1.3 compliant. This is not a drop-in replacement for
Wicket 1.2. The release is accompanied with a migration
guide<http://cwiki.apache.org/WICKET/migrate-13.html>
.

You can see Wicket in action with our live
examples<http://wicketstuff.org/wicket13> The
distribution contains the Wicket jars and all sources, including the
examples. You can download the release on one of the Apache
mirrors<http://www.apache.org/dyn/closer.cgi/wicket/1.3.0>

While we take a break recuperating from the holidays, we have begun planning
the next version: it will be Java 5 based, introduce generics into the
models, and some other nice
stuff<http://cwiki.apache.org/WICKET/wicket-14-wish-list.html>.
You can help and discuss the future of Wicket on our mailing list.

Re: [discuss] Wicket 1.3 release notes

Posted by Frank Bille <fr...@apache.org>.
I think the layout could be improved ;-)

Frank


On Jan 1, 2008 11:05 PM, Martijn Dashorst <ma...@gmail.com>
wrote:

> h1. Apache Wicket 1.3 released The Wicket team wishes everybody a happy
> new
> year and starts 2008 promising with a fresh new release: Apache Wicket 1.3
> .
> "Apache Wicket":http://wicket.apache.org is a Java open source component
> based web application framework. Apache Wicket was established as a top
> level project at the Apache Software Foundation on June 20th 2007. With
> proper mark-up/logic separation, a POJO data model, and a refreshing lack
> of
> XML, Apache Wicket makes developing web-apps simple and enjoyable again.
> Swap the boilerplate, complex debugging and brittle code for powerful,
> reusable components written with plain Java and HTML. This new release
> features some considerable improvements over previous releases and
> stabilizes several core API's. Highlights from this release: * last
> JDK-1.4release (next release will be Java 5 based) * package move from
> @wicket@ to
> @org.apache.wicket@ -- Wicket joined the Apache Software foundation and
> renaming all packages to go into the Apache namespace reflects this move *
> simplified models API -- the number of Model classes was minimized, the
> @Component@ parameter to the @get/setObject@ methods has been removed as
> it
> was not always clear which component to provide * simplified converter API
> -- converters now need two methods (see interface @IConverter@):
> @convertToObject(String, Locale)@ and @convertToString(Object, Locale)@,
> this makes rolling your own custom converters much easier * all URL's are
> now generated as relative URL's -- this means it works with zero-config
> behind a proxy server * simplified validator API -- the validator API has
> been decoupled from Wicket's form component hierarchy allowing you to
> create
> validators so that validators can be reused outside Wicket * guice support
> -- want to use Google's guice as your dependency injection framework?
> wicket-guice makes it easy: @@Inject private IService service;@ will
> inject
> the IService implementation into your Wicket component. * portlet support
> ("JSR-168":http://jcp.org/en/jsr/detail?id=168, "JSR-286":
> http://jcp.org/en/jsr/detail?id=286) -- Wicket pages can now work directly
> in a portal as portlets without changing a line of code (no separate
> component hierarchy), learn more about Wicket's portlet support in this
> presentation by Ate Douma: "Wicket portlet primer":
> http://www.slideshare.net/ate.douma/wicket-portlet-primer * switched
> logging
> API from commons-logging to slf4j * improved Ajax support -- new Ajax
> components can be added to the page and contribute new javascript
> dependencies to the page header, hide/show components using Ajax without
> workarounds (@setOutputMarkupPlaceHolderTag@) * added @<wicket:enclosure>@
> and @<wicket:container>@ tags -- @<wicket:enclosure>@ is a grouping tag
> for
> controlling visibility of markup surrounding a component,
> @<wicket:container>@ can add components' markup in places where it would
> make the page non-w3c compliant * stateless pages and components for those
> parts of your application that needs to scale * hybrid URL encoding to
> make
> search engines and your users happy (see "Thoof":http://thoof.com for an
> example in action) * nested form components -- create panels that contain
> forms and use them anywhere without having to worry about the nesting of
> forms * minimized session use by storing component hierarchy in file
> system
> (DiskPageStore) And much more small updates, upgrades and new features. As
> there have been API breaks you will need to do some work on your existing
> applications to make it 1.3 compliant. This is not a drop-in replacement
> for
> Wicket 1.2. The release is accompanied with a "migration guide":
> http://cwiki.apache.org/WICKET/migrate-13.html and "live examples":
> http://wicketstuff.org/wicket13 (the examples are part of the
> distribution).
> The distribution contains the Wicket jars and all sources. You can
> download
> the release here on one of the "Apache mirrors":
> http://www.apache.org/dyn/closer.cgi/wicket/1.3.0 While we take a break
> recuperating from the holidays, we have begun planning the next version:
> it
> will be Java 5 based, introduce generics into the models, and some other
> "nice stuff":http://cwiki.apache.org/WICKET/wicket-14-wish-list.html. You
> can help and discuss the future of Wicket on our mailing list.
>