The return type idea sounds like something that will be useful for certain scenerios, but I don't think I want to introduce another chain of subclasses with AjaxComponent.
I think the intent is to move away from this pattern and use something more flexible, like an object to add things into. (IE markup writer, or equivalent) On 2/23/06, Edgar Chan Carrillo <[EMAIL PROTECTED]> wrote: > > Hi!! .. In my opinion i think the response part could be done in more > natural way, something like the listener methods activate the response page > with its return type. > > http://jakarta.apache.org/tapestry/UsersGuide/listenermethods.html > > > Using the return type of the listeners and creating a new base > AjaxComponent type that can be contributed later with json,xml or html > implementations we could response not only ajax but whatever content type we > need, for example: > > @meta("ajaxType:json") > public AjaxComponent myListenerMethod(){ > return myJsonComponent; > } >
