Tynamo

RouterDispatcher gets initialized/constructed but is never called during dispatch

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Not A Bug
  • Affects Version/s: routing-0.0.2
  • Fix Version/s: None
  • Component/s: routing
  • Labels:
    None
  • Number of attachments :
    0

Description

See TYNAMO-137 for more detailed information on the issue.

In the above setting, the RouterDispatcher's dispatch() method never gets called using tapestry 5.3.2

The RouterDispatcher will be initialized with the correct routing information, though.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Alejandro Scandroli added a comment -

As documented in the tapestry-routing guide:

The only caveat with the current implementation is that you can't use Index pages. I mean pages named "*Index"
The way Tapestry handles *Index pages prevents the module from working properly.

Do you have any Index page in your project?

Show
Alejandro Scandroli added a comment - As documented in the tapestry-routing guide: The only caveat with the current implementation is that you can't use Index pages. I mean pages named "*Index" The way Tapestry handles *Index pages prevents the module from working properly. Do you have any Index page in your project?
Hide
Permalink
Carsten Klein added a comment - - edited

Yes, I do. So it all boils down to the problem of "he who can read...".

Well, trying to figure out what is going on behind the curtains, I adjusted the registration of the RouterDispatcher so that it will be called before:PageRender. This did the trick, even with a root Index page.

Don't know whether this will break other parts of the application, though.

Show
Carsten Klein added a comment - - edited Yes, I do. So it all boils down to the problem of "he who can read...". Well, trying to figure out what is going on behind the curtains, I adjusted the registration of the RouterDispatcher so that it will be called before:PageRender. This did the trick, even with a root Index page. Don't know whether this will break other parts of the application, though.
Hide
Permalink
Alejandro Scandroli added a comment -

One of the main hidden features of the module is the "overridability" of routes. Real pages should always take precedence over a route. This is a key feature for tapestry-model, without it the page customization wouldn't work.

If you put the RouterDispatcher before the PageRender your tapestry pages won't take precedence over the routes.

Show
Alejandro Scandroli added a comment - One of the main hidden features of the module is the "overridability" of routes. Real pages should always take precedence over a route. This is a key feature for tapestry-model, without it the page customization wouldn't work. If you put the RouterDispatcher before the PageRender your tapestry pages won't take precedence over the routes.
Hide
Permalink
Carsten Klein added a comment -

Okay, that is fine with me, currently using a patched version of your module, but will revert it back to the original as soon as I get more familiar with tapestry.
Will close this.

Show
Carsten Klein added a comment - Okay, that is fine with me, currently using a patched version of your module, but will revert it back to the original as soon as I get more familiar with tapestry. Will close this.

People

  • Assignee:
    Unassigned
    Reporter:
    Carsten Klein
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: