Hi Thijs, thanks for your help, but you don't have to hurry. We faked the whole thing by running our Wicket-App inside an iFrame in Liferay. It is just for a showcase.
So we don't need it right now. Thanks anyway, Benjamin On Thu, May 15, 2008 at 9:14 PM, Thijs Vonk <[EMAIL PROTECTED]> wrote: > Hi Benjamin > I'll see if I have some time left tomorrow, otherwise hopefully before next > tuesday. > > Thijs > > > Benjamin Ernst wrote: > >> Hi Thijs, >> >> We are currently trying to integrate Liferay 5 with wicket 1.3. Can you >> give >> us the advise you offered? That would be very nice. >> >> Thank you in advance, >> Benjamin >> >> On Mon, May 5, 2008 at 11:33 PM, Thijs Vonk <[EMAIL PROTECTED]> wrote: >> >> >> >>> Hi, >>> >>> Currently without building wicket against Liferay (using >>> com.liferay.portlet.renderresponseimpl, instead of >>> javax.portlet.renderresponse) it is not possible 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 Quninne wrote: >>> >>> >>> >>>> 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 jsr-286 now. However >>>>> while doing this I've noticed that Liferay has still some major issues >>>>> regarding jsr-286. Especially regarding setting properties on the >>>>> response >>>>> (essentially setting response headers, cookies, etc) there is still >>>>> some >>>>> work to be done. They also don't support the >>>>> MARKUP_HEAD_ELEMENT_SUPPORT >>>>> feaure jet, what would be a really nice addition because of the CSS and >>>>> JS >>>>> files wicket adds to it's pages. >>>>> Comment and vote on http://support.liferay.com/browse/LEP-5828. and >>>>> track it to follow the property changes >>>>> >>>>> I'm also planning on opening a Wicket-jira issue so that you can >>>>> track the progress of the wicket implementation. But we will have to >>>>> wait at >>>>> least until the portlet 2.0 specifications get official and added to a >>>>> maven >>>>> repository before we can add anything to the wicket code base. Besides >>>>> that >>>>> it's a lot of work and I'm doing this in my free hours so don't get >>>>> over >>>>> excited just jet :). >>>>> >>>>> I'll post a message on the list when I open the jira issue, and I'll >>>>> attach patches to that issue as soon as I feel confident about the work >>>>> I've >>>>> been doing. >>>>> >>>>> I hope that answers your questions a bit. >>>>> Thijs >>>>> >>>>> >>>>> gaugat wrote: >>>>> >>>>> >>>>> >>>>> >>>>>> I've read in the forums, that it is better to wait for Liferay 5 >>>>>> (JSR >>>>>> 286) to >>>>>> develop portlets in Apache Wicket. So has anyone developed portlets >>>>>> using >>>>>> Wicket and deployed them in Liferay 5?. If you have, is there a >>>>>> sample >>>>>> wicket portlet posted somewhere that I could look at? Are there >>>>>> still >>>>>> issues >>>>>> with Wicket and Liferay? >>>>>> >>>>>> >>>>>> >>>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>>>> For additional commands, e-mail: [EMAIL PROTECTED] >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >>> >>> >> >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
