many thanks for your effort... this
is definitly the way to go and a step towards giving more value to cocoon
as you know we are searching for alternatives
in our product-development which is currently cocoon / cforms based. your
wicket reader seems very interesting for us... as soon as I have
some time I will try it out!
BTW: does the reader also work for cocoon
Reinhard Pötz <firstname.lastname@example.org>
Please respond to
Cocoon3 <-> Wicket integration
Since I was asked several times off-list and there have also been some
mails on the users list asking about the best way to integrate Cocoon
with Wicket, I invested some time into a first implementation. Actually
there are five ideas that I have:
a) An IRequestTargetUrlCodingStrategy wrapping a Cocoon sitemap
b) An IRequestTargetUrlCodingStrategy wrapping a Cocoon pipeline
c) A page component wrapping a Cocoon pipeline
d) A Wicket reader to be used in Cocoon sitemaps
e) Wicket generator/transformer, again to be used in sitemaps
a) and b) are useful to add a couple of pipelines to your Wicket
application. c) helps if you want to use a Cocoon pipeline to provide
the content of some parts of a page.
d) and e) help to run a Wicket application in parallel with Cocoon while
Cocoon remains the "leading" framework.
- o -
I added implementations and samples for a, c and d to the SVN. The
generic parts are in the cocoon-wicket module, the Cocoon/Wicket samples
in cocoon-samples and the Wicket/Cocoon samples in
I also wrote some initial documentation that you can find at
- o -
Currently it's rather a proof-of-concept (especially the reader) than
something that you should use in production, but hopefully a first step
and a basis for further discussions if this is of help to others.
Let me know if this is of interest to you and what you think about the
And finally many thanks to Steven who helped me to hunt down some
bugs in the reader component.