Tapestry
  1. Tapestry
  2. TAPESTRY-894

SpecificationResolverDelegate not consulted if component class found first

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 4.0
    • Fix Version/s: 4.1.1
    • Component/s: Framework
    • Labels:
      None

      Description

      I am attempting to put my components under WEB-INF/component. I used the example from the wiki: http://wiki.apache.org/jakarta-tapestry/PagesAndComponentsInWEB-INF.

      My component's .jwc file is not found. Tracing through the code I see that in ComponentSpecificationResolverImpl.searchForComponent(IRequestCycle), if the .jwc file is not found in the usual locations, a search is done for the class. If the class is found, it is assumed the .jwc must be in WEB-INF and the configured SpecificationResolverDelegate is never consulted.

      This does not seem correct. Shouldn't all efforts to locate the .jwc be exhausted before searching for the class?

        Activity

          People

          • Assignee:
            Jesse Kuhnert
            Reporter:
            Mark Reynolds
          • Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development