Hi All, many thanks for pointing me to the right direction.
Regards Dipu On 8/30/07, Matej Knopp <[EMAIL PROTECTED]> wrote: > > Hi Ate, > > thanks for the examples. The progress is tremendous. Awesome. > > -Matej > > On 8/30/07, Ate Douma <[EMAIL PROTECTED]> wrote: > > > > Martijn Dashorst wrote: > > > I think it is in a branch in our apache repo: > > > > > > > > > http://svn.apache.org/repos/asf/wicket/branches/wicket-1.3-portlet-support/ > > Yes, and there is a corresponding JIRA issue with several subtasks which > I > > use for tracking the current state (and some minimal documentation): > > > > https://issues.apache.org/jira/browse/WICKET-647 > > > > If you are interested in testing that out, I've provided a downloadable > > Jetspeed-2 installer which the wicket-examples application deployed as > > portlet > > application here: > > > > http://people.apache.org/~ate/wicket/ > > > > Note though the above branch was created on July 14 from the trunk at > that > > time (r547242), and the portlet-support (as currently checked in) isn't > > perfect or > > without some serious bugs yet. > > > > But, I've started working on a updated version of the portlet-support > this > > week which is based on the latest 1.3.0-beta3 release and it is > > progressing rather well. > > I hope to commit this update tomorrow or else early next week the > latest. > > For that, I plan to create a new branch, > > wicket-1.3.0-beta3-portlet-support, as merging back in all the trunk > > changes since the branch (reliably) turned out to > > be far too much work. > > > > So, I started from "scratch" again, applying my original changes by > hand, > > bit by bit (man, being on a branch of a project which moves as quickly > as > > Wicket is > > painful...). > > Which turned out to be not a bad idea after all: I cleaned up and > improved > > several changes along the lines as well as refactored several new > classes > > and methods > > names to better reflect their purpose. Luckily, as the new > portlet-support > > (in contrast to the one from 1.2.x) is now using transparent "bridging" > > wicket to the > > portlet environment, those internal changes didn't have any effect on > the > > usage. > > > > Anyway, you will all soon see that the portlet-support has progressed > > nicely, to the point I think it covers many to most standard use-cases > > (albeit there still > > are and always will be a few area's where portlet support is difficult > or > > even formally impossible to provide). > > > > The nicest part I think is that it turned out to require very little > > changes to the wicket core, and AFAIK all of those are transparent, > meaning > > these changes > > have zero effect for existing plain servlet based applications! > > > > In my opinion, it should be ready for trunk integration soon now (after > > proper review of course), we just need to find and agree upon the right > time > > frame. > > > > Right now I'm working on getting popup/modal windows also working > > properly, and once that's finished I'll check the stuff in under the new > > branch. > > > > One last important fact I need to mention is that I've build some of the > > portlet-support features upon the anticipated new Portlet 2.0 API > > (JSR-286, of which > > I'm also an EG member). As JSR-286 isn't released yet (but very soon > > now...), and no (formal) implementations exists or are even allowed, I > have > > defined some > > supporting interfaces, specifically for header contributions and > Portlet > > ResourceURLs. > > To be able to actually run wicket with the new portlet-support within a > > portal, you'll need portal specific implementations for these > interfaces. > > As soon as JSR-286 is available as well as supporting portals, those > > interfaces can be retrofitted back upon JSR-286 APIs and you won't need > such > > proprietary > > implementations anymore. > > > > For my own testing, and because I'm also a Jetspeed committer, I've > > already provided Jetspeed-2 specific support implementations. > > Since the latest Jetspeed-2.1.2 release, these are provided > out-of-the-box > > with the portal itself. > > For more information about this, see: > > http://issues.apache.org/jira/browse/PB-65 > > > > So, for now, you might be required to test and experiment using > > Jetspeed-2, although I think I already saw someone report it running on > > Liferay as well. > > > > Regards, > > > > Ate > > > > > > > > Martijn > > > > > > On 8/30/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > > >> it has moved to wicket-stuff because none of the core committers have > > time > > >> to keep it up to date. i believe Ate was reworking it into something > > better, > > >> his work in progress is in wicket-stuff > > >> > > >> -igor > > >> > > >> On 8/30/07, Dipu Seminlal <[EMAIL PROTECTED]> wrote: > > >>> Hi All, > > >>> > > >>> I checked out the wicket trunk and found that the Portlet package > has > > >>> disappeared from where it was. > > >>> Has it been moved to somewhere else or did the Portlet support got > > removed > > >>> totally ? > > >>> What is the future plans for the Portlet support in wicket. > > >>> > > >>> Thanks > > >>> Dipu > > >>> > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > >
