Thiago,
firstly, I assumed you meant "Normal" == "the Tapestry Dispatcher", but
my point is that the 4 Tapestry built-in Dispatchers (AssetDispatcher,
ComponentEventDispatcher, PageRenderDispatcher and RootPathDispatcher)
are no different to my JonathansFunkyDispatcher, and nor should they.
Anyway, it seems Howard has a new interface in Tap 5.1.
BTW, after your comment about loading a page just to check the
annotations, I went looking at the ComponentClassResolver. It has a neat
method: resolvePageNameToClassName(String logicalPageName). Then I can
ask a classloader for the class, and bingo! No more page instanciation.
Ciao,
Jonathan
On 06/02/2009 11:22, Thiago H. de Paula Figueiredo wrote:
On Thu, Feb 5, 2009 at 10:43 PM, Jonathan O'Connor<ninki...@eircom.net> wrote:
Thiago,
Hi!
I guess you want the Class if your doing annotation based protection, and
the string if you have some sort of map.
You're right. My needs are different from yours. :)
But, as Daniel mentioned, you can
get a ComponentSource, and convert the string to a Class, so no problems
there.
This isn't the best way to do it because a component or page would be
instantiated just for the sake of knowing what page/component class.
The problem is deciding what a normally dispatched request is.
I could have chosen better words. When I said normal, I meant
"dispatched by the Tapestry dispatcher". ;)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
