Hi Geert, Thanks for the pointers. I'll do that. What I've found out is that parent / child continuation support does not seem to work. I've got an issue as the parent continuation id is never set in the child one. Do you think it'll be solved in the snapshot ( I want to use it to support back links).
Regarding continuation parameter, I couldn't find anything that relates to my problem, probably because I'l lacking on how the internal of continuations work. What I've done to support it is the following: use com .uwyn .rife .continuations .ContinuationContext.getActiveContext().setCallAnswer(parameter) to set a parameter, and using the callanswer to to create the state object in the call state, and then modifying the callTargetRetriever to pass it as a parameter of the constructor for my child continuation class. It's a bit tedious but it works. Do you think it'd be possible to add a ... parameter to the call method that will be able to pass the parameters ? It'd make my life much easyer. Otherwise, it was really simple to hook Tapestry & Rife together, just a mater of creating several classes, and a tapestry service to make the thing work L. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "rife-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rife-users?hl=en -~----------~----~----~----~------~----~------~--~---
