((RequestCycle) cycle).setServiceParameters(ret);
> }
> else { //dont work
> cycle.activate(NoviaMail_ReadMail);
> }
> }
>
> Any help will be apprecated.
> Thanks
>
> MattHouston
>
--
View this message in context:
}
>> > > else { //dont work
>> > > cycle.activate(NoviaMail_ReadMail);
>> > > }
>> > > }
>> > >
>> > > Any help will be apprecated.
>> > > Thanks
>> > >
>> > &g
I should clarify, this all works when using the normal core ajax
services provided in 4.1.1, not specifically in the XTile service.
On 12/6/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
FYI, this all "just works" as expected in t 4.1.1. (the solution is
still a little questionable but it's the be
FYI, this all "just works" as expected in t 4.1.1. (the solution is
still a little questionable but it's the best default behavior I could
think of so far)
On 12/6/06, Robert Zeigler <[EMAIL PROTECTED]> wrote:
cycle.activate will make the "activated" page be the page that renders.
However... the
cycle.activate will make the "activated" page be the page that renders.
However... the xtile service doesn't result in a page render. It results
in an "ajax" response; hence, cycle.activate won't work. What you might
consider doing is putting the url of the page you want to activate into
the se
.
Thanks
MattHouston
--
View this message in context:
http://www.nabble.com/XTile-and-cycle.activate-tf2769341.html#a7723360
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PR
