Hi,
On Thu, Jan 8, 2015 at 10:45 PM, Joachim Schrod jsch...@acm.org wrote:
On 01/08/15 08:15, Ernesto Reinaldo Barreiro wrote:
Hi,
I would use server side activation. Implemented as in
1- You can create your own events, e.g. [1]. One that is a wrapper of
AJAX
request target (e.g.
Hi,
Apologies, I might have not understood your requirements correctly.
Comments inline.
I don't grasp your intent completely. I get that I can define my
own event classes server-side. I don't get how that helps me client
side.
You can do want at server side to trigger something or not at
On 01/08/15 08:15, Ernesto Reinaldo Barreiro wrote:
Hi,
I would use server side activation. Implemented as in
1- You can create your own events, e.g. [1]. One that is a wrapper of AJAX
request target (e.g. AtivateLinksEvent).
2- Your links will listen for AtivateLinksEvents and decide
If I¹m understanding you correctly, wouldn¹t it be sufficient to code this
as
a simple AjaxLink, which responds with a regular AJAX
update when the link is disabled, or uses setResponsePage when it¹s
enabled?
Boris
On 1/7/15, 9:15 PM, Joachim Schrod jsch...@acm.org wrote:
Hi,
I have a class
On 01/08/15 15:50, Boris Goldowsky wrote:
If I¹m understanding you correctly, wouldn¹t it be sufficient to code this
as
a simple AjaxLink, which responds with a regular AJAX
update when the link is disabled, or uses setResponsePage when it¹s
enabled?
The link in question delivers a PDF
Hi,
I would use server side activation. Implemented as in
1- You can create your own events, e.g. [1]. One that is a wrapper of AJAX
request target (e.g. AtivateLinksEvent).
2- Your links will listen for AtivateLinksEvents and decide if they should
be enabled or not (and add themselves to ART