[ http://issues.apache.org/jira/browse/TAPESTRY-894?page=all ]
Jesse Kuhnert updated TAPESTRY-894:
-----------------------------------
Fix Version/s: 4.1.1
> SpecificationResolverDelegate not consulted if component class found first
> --------------------------------------------------------------------------
>
> Key: TAPESTRY-894
> URL: http://issues.apache.org/jira/browse/TAPESTRY-894
> Project: Tapestry
> Issue Type: Bug
> Components: Framework
> Affects Versions: 4.0
> Reporter: Mark Reynolds
> Assigned To: Jesse Kuhnert
> Fix For: 4.1.1
>
> Attachments: ComponentSpecificationResolverImpl.java.patch
>
>
> 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?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
