It's hard to tell. I'm familiar enough with the XtileService to know if it should be calling cycle.activate(page) or not before calling your method. You could probably log it as a bug I guess.
On 1/11/06, Ben Dotte <[EMAIL PROTECTED]> wrote: > > Well the stuff I'm working on is pre-existing and already has a lot of > logic built around it (I'm just making a small modification that > happened to need the current page). I guess I'm just looking to find out > if I should submit a bug report for this or if it is just a consequence > of the way callbacks are handled when using Ajax. From your post, I take > it this is a bug then? > > -----Original Message----- > From: Jesse Kuhnert [mailto:[EMAIL PROTECTED] > Sent: Wednesday, January 11, 2006 1:52 PM > To: Tapestry users > Subject: Re: XTile listener can't get current page? > > You could always try using http://tacos.sourceforge.net, I don't think > you'll experience the same issues there, unless there is something tacos > doesn't provide that you need? > > On 1/11/06, Ben Dotte <[EMAIL PROTECTED]> wrote: > > > > I am using XTile on a page something like this: > > > > > > > > <span jwcid="@contrib:XTile" listener="ognl:listeners.handleCallback" > > sendName=.....> > > > > > > > > public void handleCallback(IRequestCycle cycle) > > > > { > > > > if (cycle == null) > > > > { > > > > System.out.println("cycle is null!"); > > > > } > > > > else if (cycle.getPage() == null) > > > > { > > > > System.out.println("cycle.getPage() is > null!"); > > > > } > > > > } > > > > > > > > This returns: > > > > cycle.getPage() is null! > > > > > > > > So, the cycle is not null, but it doesn't know what the active page > is. > > I also tried injecting the request cycle instead of using the > parameter > > in handleCallback() but got the same result. I think I have a > workaround > > that should work instead but is this something I have to live with > when > > using Ajax, or could there be a bug involved here? > > > > > > > > Ben > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
