Thanks, Igor.
Does that mean, then, there's no native support for this sort of thing?
ClientLink would help me if:
A) The return-value of the function it generates is the return value
of the Listener (e.g. a JSON String)
B) There were a way to specify a JavaScript function that handles the
response from A), at the time of the AJAX response. (I assume the
function ClientLink generates is asynchronous).
I'm probably going down the wrong path hoping to be able to use Tapestry
listeners as web services -- I saw "Ajax" and "JSON" and got excited
that I could take out the DWR middle-man and implement services directly
in my Tapestry pages.
Thanks!
Jim
Igor Drobiazko wrote:
Have a look at the ClientLink component in Tacos.
http://andyhot.gr/tacos-demo/ClientLink.html
Please see here how to use it:
http://tacos.sourceforge.net/tacos4.1/apidocs/net/sf/tacos/components/ClientLink.html
Hope this helps
On Thu, Feb 14, 2008 at 6:57 PM, Jim <[EMAIL PROTECTED]> wrote:
Hello!
I'm going through the Ajax documentation, and I'm all set as far as
tying @EventListener methods to client-side events. However, I'm a
little confused as to how the client is to receive/process the server
response.
I do see how the core Tapestry components have an updateComponents
property, and those components may be injected into the backing
page-class and updated programmatically.
Does this mean, however, that the only way to get a response back to the
client is by updating a component property?
Ideally, I'm looking for something like DWR behavior, where I could
programmatically (via client-side JavaScript) call a Tapestry listener
and get a JSON response back for arbitrary JS processing. Is there a
reasonable way to do this using the T4.1 Ajax framework? Or is this
outside the scope of what T4.1 is intending with its Ajax support?
Thanks,
Jim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
