You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Matthew B. Payne (JIRA)" <ta...@jakarta.apache.org> on 2006/07/28 19:57:15 UTC

[jira] Commented: (TAPESTRY-1026) PageSpecificationResolverImpl doesn't search "implict" page specifications/templates in all the right places.

    [ http://issues.apache.org/jira/browse/TAPESTRY-1026?page=comments#action_12424135 ] 
            
Matthew B. Payne commented on TAPESTRY-1026:
--------------------------------------------

Don't have a patch, but start looking in code around line 189 in PageSpecificationResolverImpl 

e.g. 
====> this part looks for just a template in /{webroot}/admin/ManageUsers.html

    // The wierd one ... where we see if there's a template in the application root
            // location.

            String templateName = _simpleName + "." + getTemplateExtension();

            Resource templateResource = getContextRoot().getRelativeResource(templateName);

            if (_log.isDebugEnabled())
                _log.debug(ResolverMessages.checkingResource(templateResource));

            if (templateResource.getResourceURL() != null)
            {
                setupImplicitPage(templateResource, namespaceLocation);
                return;
            }
====> after this it should search /WEB-INF/csc/admin/ManageUsers.html



> PageSpecificationResolverImpl doesn't search "implict" page specifications/templates in all the right places.
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: TAPESTRY-1026
>                 URL: http://issues.apache.org/jira/browse/TAPESTRY-1026
>             Project: Tapestry
>          Issue Type: Bug
>    Affects Versions: 4.0.2
>            Reporter: Matthew B. Payne
>
> Page specifications are supposed to be optional.  However, the PageSpecificationResolverImpl does not find templates in all the same places/paths that is searches for actual .page specifications. 
> java class for page -->
> com.pennmutual.csc.pages.admin.ManageUsers
> My .application file
> [code]
> <?xml version="1.0"?>
> <!DOCTYPE application PUBLIC 
>   "-//Apache Software Foundation//Tapestry Specification 4.0//EN" 
>   "http://jakarta.apache.org/tapestry/dtd/Tapestry_4_0.dtd">
>   
> <application>  
>   <meta key="org.apache.tapestry.page-class-packages" value="com.pennmutual.csc.pages"/>
>   <meta key="org.apache.tapestry.component-class-packages" value="com.pennmutual.csc.components"/>
>   <page name="Home" specification-path="AccountHome.page"/>
>   <library id="Contrib" specification-path="classpath:/org/apache/tapestry/contrib/Contrib.library"/>	
>   <library id="tacos" specification-path="/net/sf/tacos/Tacos.library"/>
>   
> </application>
> [/code]
> e.g. default package is. com.pennmutual.csc.pages
> root templates/specs are in /WEB-INF/csc
> The url of the page that is not found is http://localhost:8080/cee/admin/ManageUsers.html
> If I put a page/specification file in /WEB-INF/csc/admin the page is found (Correct)
> If I delete that page specification and just put my template in {webroot}/admin/, page specification is implicitly created (Correct).
> ***If I put my template in {webroot}/WEB-INF/csc/admin with no .page specification, the template is not found and no "implicit" specfication is create (InCorrect).**

-- 
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org