Hey guys,
Finally I've finished the blueprint integration of pax-wicket. For the
moment I'm at testing those changes with some real world projects I
wanted to port from spring to blueprint forever by now. If everything
goes smooth I'm convinced that 0.7.0 should be stable enough for a
release (I expect Wednesday or Thursday). If you like to help me
evaluating the upcoming release you can use the snapshots available at
[1] (I push them manually for each commit right now, because of an
Hudson issue). Please be aware that there are three big know usability
issues right now with pax-wicket (PAXWICKET-27, PAXWICKET-126,
PAXWICKET-154).
Workarounds:
PAXWICKET-27
=============
For each library you like to work with and which does not provide a
pax-wicket service (one of application, pagefactory, contentfactory or
aggregation point) you have to manually register a ClassResolver and
InjectionResolver service.
PAXWICKET-126
=============
To make injection work pax-wicket uses cglib to wrap your properties.
The drawback with this approach is that you have to manually import
some packages which you do not reference directly. In detail those
are:
org.apache.wicket.behavior;version="${wicket.dependency.version}",\
org.apache.wicket.markup.html.internal;version="${wicket.dependency.version}",\
org.apache.wicket.markup.html;version="${wicket.dependency.version}",\
org.apache.wicket.markup;version="${wicket.dependency.version}",\
org.apache.wicket.session.pagemap;version="${wicket.dependency.version}",\
org.apache.wicket.util.convert;version="${wicket.dependency.version}",\
org.apache.wicket.model;version="${wicket.dependency.version}",\
org.ops4j.pax.wicket.util.proxy;version="${project.version}", \
net.sf.cglib.core;version="${cglib.range}", \
net.sf.cglib.proxy;version="${cglib.range}", \
net.sf.cglib.reflect;version="${cglib.range}"
PAXWICKET-154
=============
To make PaxWicketBean work you have to register for each page where
you would like to make those annotations work a spring or blueprint
pageFactory in your spring or blueprint configuration file.
Since none of those issues threaten stability and I prefer the
"release early, release often" approach I plan to push out
pax-wicket-0.7.0 with those issues and release 0.8.0 one to two weeks
after providing fixes for those problems.
OK, finally: If you like to include anything else into 0.7.0 now is
the right time to push it! If you experience any last minute
instabilities please provide issues for them or post here on this
list.
Thank you very much and have fun with a better wicket ;)
Kind regards,
Andreas
[1]
http://oss.sonatype.org/content/repositories/ops4j-snapshots/org/ops4j/pax/wicket/pax-wicket-service/0.7.0-SNAPSHOT/
_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general
