to run wicket without
losing most of wickets functionality.
I can, if you want, give you a patch and some instructions to get wicket
working on liferay 5, but we are still modifying wicket and Liferay code
to get things working as we want it. So I can't guaranty anything.
Thijs
Bobby
specifications
Thijs
Bobby Quninne schreef:
You have a rough guess estimate as to a wicket release that will address
JSR-268 compliance?
Many thanks
Thijs wrote:
Hi,
Currently without building wicket against Liferay (using
com.liferay.portlet.renderresponseimpl, instead
Hi there, I am currently considering using wicket 1.3.3(and newer) with
liferay 5.
The site is going to be used for backend administration, standard CRUD
stuff.
How big a risk is it, using wicket portal and liferay?
Thanks
Thijs wrote:
Hi,
I'm working on getting wicket compatible with
Hi there,
I am currently considering using wicket to replace an existing system
developed with apache cocoon. Some of the draw backs I have noted of the
cocoon implementation is :
1. Website flow to pages is hard to determine, as well as debug when I don't
land up on the expected page.
2.
Different css ... or markup.. or language... possibly determined by user
preference... or whatever you like.
Bobby Quninne wrote:
There is a requirement that the website can be branded but LF can
completely differ. Currently branded sites look exactly the same in terms
of layout, just different
