You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Paul Cantrell <ca...@pobox.com> on 2006/05/01 06:50:53 UTC

Generic creation of an ICallback: surely there's a better way?

I want to create a generic utility method to check whether a user is  
logged in, and redirect them to a login page if necessary.

To do this, I need to create an ICallback in the general case. In  
other words, I don't know whether I'm create an ExternalCallback or a  
PageCallback or a DirectCallback or what have you. I just want to  
create a callback for whatever the current request is, if such a  
callback is possible.

Ideally, there would be a IPage.getCallback() method, or something  
like it -- but I can't find one.

I did find some code on the mailing list involving things like "if 
(this instanceof IExternalPage)" ... yuck! Surely there's a better  
way, and I'm just missing it? I've dug around in the docs and list  
archives, but can't turn anything up. ICallback isn't even mentioned  
in the user guide, as far as I can tell....

Cheers,

Paul

_________________________________________________________________
Piano music podcast: http://inthehands.com
Other interesting stuff: http://innig.net



---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org


Re: Is it time to break the list up into 3.x and 4.x?

Posted by Paul Cantrell <ca...@pobox.com>.
This is 4.x. My presumption at this point is that all issues are 4.x  
unless explicitly stated otherwise; perhaps that is a bad  
presumption. Obviously many people are still on 3.x, but 4.x has been  
out for a good while now, and in my mind, it's the default for  
discussion on the list. If somebody is still on 3.x, they should make  
a point of that.

Still, I should have mentioned that I'm on 4.0.1; sorry!

Cheers, P

On May 1, 2006, at 2:57 PM, Mark Stang wrote:

> I was wondering if this was a 4.x or a 3.x issue.  Then it occurred  
> to me that we should probably break the list up into 3 and 4.
>
>
> -----Original Message-----
> From: Paul Cantrell [mailto:cantrell@pobox.com]
> Sent: Sun 4/30/2006 10:50 PM
> To: Tapestry users
> Subject: Generic creation of an ICallback: surely there's a better  
> way?
>
> I want to create a generic utility method to check whether a user is
> logged in, and redirect them to a login page if necessary.
>
> To do this, I need to create an ICallback in the general case. In
> other words, I don't know whether I'm create an ExternalCallback or a
> PageCallback or a DirectCallback or what have you. I just want to
> create a callback for whatever the current request is, if such a
> callback is possible.
>
> Ideally, there would be a IPage.getCallback() method, or something
> like it -- but I can't find one.
>
> I did find some code on the mailing list involving things like "if
> (this instanceof IExternalPage)" ... yuck! Surely there's a better
> way, and I'm just missing it? I've dug around in the docs and list
> archives, but can't turn anything up. ICallback isn't even mentioned
> in the user guide, as far as I can tell....
>
> Cheers,
>
> Paul
>
> _________________________________________________________________
> Piano music podcast: http://inthehands.com
> Other interesting stuff: http://innig.net
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>

_________________________________________________________________
Piano music podcast: http://inthehands.com
Other interesting stuff: http://innig.net



---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org


NFJS

Posted by Mark Stang <ms...@pingidentity.com>.
Hi,
Is anyone attending NFJS in Broomfield this weekend?

regards,

Mark

Re: Is it time to break the list up into 3.x and 4.x?

Posted by "Brian K. Wallace" <br...@transmorphix.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mark Stang wrote:
> I was wondering if this was a 4.x or a 3.x issue.  Then it occurred to me that we should probably break the list up into 3 and 4.
> 
> 
Absolutely not. To do so would be to intentionally separate discussion
which, in some circumstances, spans versions. If we could all get into
the habit of not assuming a version, thereby acknowledging a common
courtesy of specifying a version when discussing, I believe issues could
be discussed in a much more fruitful manner.

The theory of "4 is common" only works on some days - there have been
days of endless "3" discussion - and then there would have to be a
decision made as to when to create a '5' list, etc.

Specifying version on a per-thread basis makes a whole lot more sense.
[Think of how much of 4 grew out of 3 discussion and it becomes a whole
lot more important to keep everything together moving forward.]

Brian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)

iD8DBQFEVm46aCoPKRow/gARAlv7AJ9OF/K+PC06yrLEkEGk34+ArVrpxgCgkifQ
QRHMwYD1B2c7DPsbs1veLHg=
=KREt
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org


Re: Is it time to break the list up into 3.x and 4.x?

Posted by Konstantin Ignatyev <kg...@yahoo.com>.
-1

I think that breaking the list is not good idea

Mark Stang <ms...@pingidentity.com> wrote: I was wondering if this was a 4.x or a 3.x issue.  Then it occurred to me that we should probably break the list up into 3 and 4.


-----Original Message-----
From: Paul Cantrell [mailto:cantrell@pobox.com]
Sent: Sun 4/30/2006 10:50 PM
To: Tapestry users
Subject: Generic creation of an ICallback: surely there's a better way?
 
I want to create a generic utility method to check whether a user is  
logged in, and redirect them to a login page if necessary.

To do this, I need to create an ICallback in the general case. In  
other words, I don't know whether I'm create an ExternalCallback or a  
PageCallback or a DirectCallback or what have you. I just want to  
create a callback for whatever the current request is, if such a  
callback is possible.

Ideally, there would be a IPage.getCallback() method, or something  
like it -- but I can't find one.

I did find some code on the mailing list involving things like "if 
(this instanceof IExternalPage)" ... yuck! Surely there's a better  
way, and I'm just missing it? I've dug around in the docs and list  
archives, but can't turn anything up. ICallback isn't even mentioned  
in the user guide, as far as I can tell....

Cheers,

Paul

_________________________________________________________________
Piano music podcast: http://inthehands.com
Other interesting stuff: http://innig.net



---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org




Is it time to break the list up into 3.x and 4.x?

Posted by Mark Stang <ms...@pingidentity.com>.
I was wondering if this was a 4.x or a 3.x issue.  Then it occurred to me that we should probably break the list up into 3 and 4.


-----Original Message-----
From: Paul Cantrell [mailto:cantrell@pobox.com]
Sent: Sun 4/30/2006 10:50 PM
To: Tapestry users
Subject: Generic creation of an ICallback: surely there's a better way?
 
I want to create a generic utility method to check whether a user is  
logged in, and redirect them to a login page if necessary.

To do this, I need to create an ICallback in the general case. In  
other words, I don't know whether I'm create an ExternalCallback or a  
PageCallback or a DirectCallback or what have you. I just want to  
create a callback for whatever the current request is, if such a  
callback is possible.

Ideally, there would be a IPage.getCallback() method, or something  
like it -- but I can't find one.

I did find some code on the mailing list involving things like "if 
(this instanceof IExternalPage)" ... yuck! Surely there's a better  
way, and I'm just missing it? I've dug around in the docs and list  
archives, but can't turn anything up. ICallback isn't even mentioned  
in the user guide, as far as I can tell....

Cheers,

Paul

_________________________________________________________________
Piano music podcast: http://inthehands.com
Other interesting stuff: http://innig.net



---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org



Re: Generic creation of an ICallback: surely there's a better way?

Posted by Henri Dupre <he...@gmail.com>.
On 5/1/06, Paul Cantrell <ca...@pobox.com> wrote:
>
> I want to create a generic utility method to check whether a user is
> logged in, and redirect them to a login page if necessary.
>
> To do this, I need to create an ICallback in the general case. In
> other words, I don't know whether I'm create an ExternalCallback or a
> PageCallback or a DirectCallback or what have you. I just want to
> create a callback for whatever the current request is, if such a
> callback is possible.



This is funny, I just hit the same issue and have been frustrated myself
with the ICallback. I bet that 90% of tapestry apps have exactly the same
authentication requirement: on a page that requires authentication, check if
user is authenticated, if not redirect to a login page and after login go
back to the original page with the same context.

I believe that this could be all wired in the tapestry framework to make
people's life easier.

Thanks,

Henri.

RE: Generic creation of an ICallback: surely there's a better way?

Posted by James Carman <ja...@carmanconsulting.com>.
Well, the three main services (Direct, Page, and External) already have
their own flavors of callbacks.  It shouldn't be difficult to add this sort
of support in.  For folks with their own implementations of IEngineService,
it'd break their code, though (adding method to the interface).

-----Original Message-----
From: Henri Dupre [mailto:henri.dupre@gmail.com] 
Sent: Friday, May 05, 2006 11:21 AM
To: Tapestry users
Subject: Re: Generic creation of an ICallback: surely there's a better way?

On 5/5/06, James Carman <ja...@carmanconsulting.com> wrote:
>
> How about if the IEngineService interface had a
> createCallback(IRequestCycle) method?  Would that help?



Definitely! This would be great.

Henri.



---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org


Re: Generic creation of an ICallback: surely there's a better way?

Posted by Henri Dupre <he...@gmail.com>.
On 5/5/06, James Carman <ja...@carmanconsulting.com> wrote:
>
> How about if the IEngineService interface had a
> createCallback(IRequestCycle) method?  Would that help?



Definitely! This would be great.

Henri.

RE: Generic creation of an ICallback: surely there's a better way?

Posted by James Carman <ja...@carmanconsulting.com>.
How about if the IEngineService interface had a
createCallback(IRequestCycle) method?  Would that help?

-----Original Message-----
From: Henri Dupre [mailto:henri.dupre@gmail.com] 
Sent: Friday, May 05, 2006 11:02 AM
To: Tapestry users
Subject: Re: Generic creation of an ICallback: surely there's a better way?

On 5/1/06, Jesse Kuhnert <jk...@gmail.com> wrote:
>
> You might not be getting a lot of responses because it sounds like a very
> tough problem to solve.
>
> Mostly because the only way you'd be able to get someone back to a state
> ~exactly~ the way it was when they were directed to login would be a
> fairly
> large hunk of work. There is all kinds of state associated with sections
> of
> an application. Some in http session, some in the client, all over the
> place.


Here is one suggestion for restoring the context of a page:
- restore all the properties
- in case of an ExternalLink, call again the external link with the exact
parameters.
With these both mecanisms, I wouldn't need to write any kind of ICallback in
my app. The state doesn't need to be exact at all but right now, taking care
of page properties has to be done 100% manually and it generates a fair
chunk of ugly code.


Thanks,

Henri.



---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org


Re: Generic creation of an ICallback: surely there's a better way?

Posted by Henri Dupre <he...@gmail.com>.
On 5/1/06, Jesse Kuhnert <jk...@gmail.com> wrote:
>
> You might not be getting a lot of responses because it sounds like a very
> tough problem to solve.
>
> Mostly because the only way you'd be able to get someone back to a state
> ~exactly~ the way it was when they were directed to login would be a
> fairly
> large hunk of work. There is all kinds of state associated with sections
> of
> an application. Some in http session, some in the client, all over the
> place.


Here is one suggestion for restoring the context of a page:
- restore all the properties
- in case of an ExternalLink, call again the external link with the exact
parameters.
With these both mecanisms, I wouldn't need to write any kind of ICallback in
my app. The state doesn't need to be exact at all but right now, taking care
of page properties has to be done 100% manually and it generates a fair
chunk of ugly code.


Thanks,

Henri.

Re: Generic creation of an ICallback: surely there's a better way?

Posted by Paul Cantrell <ca...@pobox.com>.
Well, fair enough, Jesse -- may this probably isn't as elementary as  
I presume.

Still, I'm willing to say that session and other server-side state  
may have changed since the login attempt; all I really want to repeat  
is the same attempted user action: view X, edit Y. The architecture  
of the app is such that reproducing the same HTTP request is good  
enough. And perhaps the best way of doing that really is to bypass  
Tapestry and take a direct snapshot of the HttpServletRequest, as I'm  
doing.

Still feels like a hack, though!

Cheers, P


On May 1, 2006, at 9:34 PM, Jesse Kuhnert wrote:

> You might not be getting a lot of responses because it sounds like  
> a very
> tough problem to solve.
>
> Mostly because the only way you'd be able to get someone back to a  
> state
> ~exactly~ the way it was when they were directed to login would be  
> a fairly
> large hunk of work. There is all kinds of state associated with  
> sections of
> an application. Some in http session, some in the client, all over the
> place.
>
> I think a saner approach might be to start with just getting them  
> back to
> the same IPage they were in. You can work your way out from there  
> if you
> felt like trying to re-create the state of the current request.
>
> On 5/1/06, Paul Cantrell <ca...@pobox.com> wrote:
>>
>> My original email on this topic generated discussion -- but alas, it
>> was all about whether to split this list (agreed that's a bad idea),
>> and not about the actual question.
>>
>> Quick review: I want to create an ICallback to repeat the current
>> request, regardless of what service is handling that request.
>>
>> Here's the solution I came up with. It's not a completely
>> satisfactory solution, because (1) it feels hackish, and (2) I really
>> feel like I'm doing too much work for what seems like an elementary
>> and common problem. I still feel I must be missing something, and
>> would appreciate any helpful hints!
>>
>> My page base class (this could also be a service, or whatever) just
>> fetches the raw HttpServletRequest, and passes that to a custom
>> ICallback that does its best to reproduce the request:
>>
>>
>> public abstract class ImreBasePage extends BasePage {
>>
>>      @InjectObject("service:tapestry.globals.HttpServletRequest")
>>      public abstract HttpServletRequest getRequest();
>>
>>      protected ICallback getCallback() {
>>          if(getRequest().getMethod().equals("GET"))
>>              return new RedirectCallback(getRequest());
>>          // Could try to make RedirectCallback handle POST, but it's
>> a bad idea,
>>          // at least in the case of my app.
>>          return null;
>>      }
>> }
>>
>> public class RedirectCallback implements ICallback {
>>
>>      private final URL url;
>>
>>      public RedirectCallback(URL uri) {
>>          this.url = uri;
>>      }
>>
>>      public RedirectCallback(HttpServletRequest req) {
>>          StringBuffer urlS = req.getRequestURL();
>>          if(!StringUtils.isEmpty(req.getQueryString())) {
>>              urlS.append('?');
>>              urlS.append(req.getQueryString());
>>          }
>>
>>          try {
>>              url = new URL(urlS.toString());
>>          } catch(MalformedURLException e) {
>>              throw new IllegalArgumentException("broken request gives
>> malformed URI: " + urlS, e);
>>          }
>>      }
>>
>>      public void performCallback(IRequestCycle cycle) {
>>          cycle.sendRedirect(url.toExternalForm());
>>      }
>> }
>>
>>
>> Can I improve this code? Is there some utility I'm missing that does
>> this for me? Is this a valid approach that I should be submitting to
>> Tapestry? Anyone? Anyone? Beuller?
>>
>> This is on Tapestry 4.0.1, BTW. :P
>>
>> Cheers,
>>
>> Paul
>>
>>
>> On Apr 30, 2006, at 11:50 PM, Paul Cantrell wrote:
>>
>> > I want to create a generic utility method to check whether a user
>> > is logged in, and redirect them to a login page if necessary.
>> >
>> > To do this, I need to create an ICallback in the general case. In
>> > other words, I don't know whether I'm create an ExternalCallback or
>> > a PageCallback or a DirectCallback or what have you. I just want to
>> > create a callback for whatever the current request is, if such a
>> > callback is possible.
>> >
>> > Ideally, there would be a IPage.getCallback() method, or something
>> > like it -- but I can't find one.
>> >
>> > I did find some code on the mailing list involving things like "if
>> > (this instanceof IExternalPage)" ... yuck! Surely there's a better
>> > way, and I'm just missing it? I've dug around in the docs and list
>> > archives, but can't turn anything up. ICallback isn't even
>> > mentioned in the user guide, as far as I can tell....
>> >
>> > Cheers,
>> >
>> > Paul
>>
>> _________________________________________________________________
>> Piano music podcast: http://inthehands.com
>> Other interesting stuff: http://innig.net
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: tapestry-user- 
>> help@jakarta.apache.org
>>
>>
>
>
> --
> Jesse Kuhnert
> Tacos/Tapestry, team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind.

_________________________________________________________________
Piano music podcast: http://inthehands.com
Other interesting stuff: http://innig.net



---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org


Re: Generic creation of an ICallback: surely there's a better way?

Posted by Jesse Kuhnert <jk...@gmail.com>.
You might not be getting a lot of responses because it sounds like a very
tough problem to solve.

Mostly because the only way you'd be able to get someone back to a state
~exactly~ the way it was when they were directed to login would be a fairly
large hunk of work. There is all kinds of state associated with sections of
an application. Some in http session, some in the client, all over the
place.

I think a saner approach might be to start with just getting them back to
the same IPage they were in. You can work your way out from there if you
felt like trying to re-create the state of the current request.

On 5/1/06, Paul Cantrell <ca...@pobox.com> wrote:
>
> My original email on this topic generated discussion -- but alas, it
> was all about whether to split this list (agreed that's a bad idea),
> and not about the actual question.
>
> Quick review: I want to create an ICallback to repeat the current
> request, regardless of what service is handling that request.
>
> Here's the solution I came up with. It's not a completely
> satisfactory solution, because (1) it feels hackish, and (2) I really
> feel like I'm doing too much work for what seems like an elementary
> and common problem. I still feel I must be missing something, and
> would appreciate any helpful hints!
>
> My page base class (this could also be a service, or whatever) just
> fetches the raw HttpServletRequest, and passes that to a custom
> ICallback that does its best to reproduce the request:
>
>
> public abstract class ImreBasePage extends BasePage {
>
>      @InjectObject("service:tapestry.globals.HttpServletRequest")
>      public abstract HttpServletRequest getRequest();
>
>      protected ICallback getCallback() {
>          if(getRequest().getMethod().equals("GET"))
>              return new RedirectCallback(getRequest());
>          // Could try to make RedirectCallback handle POST, but it's
> a bad idea,
>          // at least in the case of my app.
>          return null;
>      }
> }
>
> public class RedirectCallback implements ICallback {
>
>      private final URL url;
>
>      public RedirectCallback(URL uri) {
>          this.url = uri;
>      }
>
>      public RedirectCallback(HttpServletRequest req) {
>          StringBuffer urlS = req.getRequestURL();
>          if(!StringUtils.isEmpty(req.getQueryString())) {
>              urlS.append('?');
>              urlS.append(req.getQueryString());
>          }
>
>          try {
>              url = new URL(urlS.toString());
>          } catch(MalformedURLException e) {
>              throw new IllegalArgumentException("broken request gives
> malformed URI: " + urlS, e);
>          }
>      }
>
>      public void performCallback(IRequestCycle cycle) {
>          cycle.sendRedirect(url.toExternalForm());
>      }
> }
>
>
> Can I improve this code? Is there some utility I'm missing that does
> this for me? Is this a valid approach that I should be submitting to
> Tapestry? Anyone? Anyone? Beuller?
>
> This is on Tapestry 4.0.1, BTW. :P
>
> Cheers,
>
> Paul
>
>
> On Apr 30, 2006, at 11:50 PM, Paul Cantrell wrote:
>
> > I want to create a generic utility method to check whether a user
> > is logged in, and redirect them to a login page if necessary.
> >
> > To do this, I need to create an ICallback in the general case. In
> > other words, I don't know whether I'm create an ExternalCallback or
> > a PageCallback or a DirectCallback or what have you. I just want to
> > create a callback for whatever the current request is, if such a
> > callback is possible.
> >
> > Ideally, there would be a IPage.getCallback() method, or something
> > like it -- but I can't find one.
> >
> > I did find some code on the mailing list involving things like "if
> > (this instanceof IExternalPage)" ... yuck! Surely there's a better
> > way, and I'm just missing it? I've dug around in the docs and list
> > archives, but can't turn anything up. ICallback isn't even
> > mentioned in the user guide, as far as I can tell....
> >
> > Cheers,
> >
> > Paul
>
> _________________________________________________________________
> Piano music podcast: http://inthehands.com
> Other interesting stuff: http://innig.net
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>


--
Jesse Kuhnert
Tacos/Tapestry, team member/developer

Open source based consulting work centered around
dojo/tapestry/tacos/hivemind.

Re: Generic creation of an ICallback: surely there's a better way?

Posted by Paul Cantrell <ca...@pobox.com>.
My original email on this topic generated discussion -- but alas, it  
was all about whether to split this list (agreed that's a bad idea),  
and not about the actual question.

Quick review: I want to create an ICallback to repeat the current  
request, regardless of what service is handling that request.

Here's the solution I came up with. It's not a completely  
satisfactory solution, because (1) it feels hackish, and (2) I really  
feel like I'm doing too much work for what seems like an elementary  
and common problem. I still feel I must be missing something, and  
would appreciate any helpful hints!

My page base class (this could also be a service, or whatever) just  
fetches the raw HttpServletRequest, and passes that to a custom  
ICallback that does its best to reproduce the request:


public abstract class ImreBasePage extends BasePage {

     @InjectObject("service:tapestry.globals.HttpServletRequest")
     public abstract HttpServletRequest getRequest();

     protected ICallback getCallback() {
         if(getRequest().getMethod().equals("GET"))
             return new RedirectCallback(getRequest());
         // Could try to make RedirectCallback handle POST, but it's  
a bad idea,
         // at least in the case of my app.
         return null;
     }
}

public class RedirectCallback implements ICallback {

     private final URL url;

     public RedirectCallback(URL uri) {
         this.url = uri;
     }

     public RedirectCallback(HttpServletRequest req) {
         StringBuffer urlS = req.getRequestURL();
         if(!StringUtils.isEmpty(req.getQueryString())) {
             urlS.append('?');
             urlS.append(req.getQueryString());
         }

         try {
             url = new URL(urlS.toString());
         } catch(MalformedURLException e) {
             throw new IllegalArgumentException("broken request gives  
malformed URI: " + urlS, e);
         }
     }

     public void performCallback(IRequestCycle cycle) {
         cycle.sendRedirect(url.toExternalForm());
     }
}


Can I improve this code? Is there some utility I'm missing that does  
this for me? Is this a valid approach that I should be submitting to  
Tapestry? Anyone? Anyone? Beuller?

This is on Tapestry 4.0.1, BTW. :P

Cheers,

Paul


On Apr 30, 2006, at 11:50 PM, Paul Cantrell wrote:

> I want to create a generic utility method to check whether a user  
> is logged in, and redirect them to a login page if necessary.
>
> To do this, I need to create an ICallback in the general case. In  
> other words, I don't know whether I'm create an ExternalCallback or  
> a PageCallback or a DirectCallback or what have you. I just want to  
> create a callback for whatever the current request is, if such a  
> callback is possible.
>
> Ideally, there would be a IPage.getCallback() method, or something  
> like it -- but I can't find one.
>
> I did find some code on the mailing list involving things like "if 
> (this instanceof IExternalPage)" ... yuck! Surely there's a better  
> way, and I'm just missing it? I've dug around in the docs and list  
> archives, but can't turn anything up. ICallback isn't even  
> mentioned in the user guide, as far as I can tell....
>
> Cheers,
>
> Paul

_________________________________________________________________
Piano music podcast: http://inthehands.com
Other interesting stuff: http://innig.net



---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org