You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Marcus Schulte (JIRA)" <de...@tapestry.apache.org> on 2007/04/24 13:36:15 UTC
[jira] Reopened: (TAPESTRY-1396) Specless components in libraries
don't get their assets properly resolved
[ https://issues.apache.org/jira/browse/TAPESTRY-1396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcus Schulte reopened TAPESTRY-1396:
--------------------------------------
Thanks for the quick fix! However I'm not yet entirely happy with it.
Currently the template is resolved relative to the library's spec. If you specify sub-packages for your components or pages this is a bit counter-intuitive.
As far as I can see org.apache.tapestry.resolver.ComponentSpecificationResolverImpl.searchForComponentClass() should set the virtual ".jwc" relative to the component-class not relative to the namespaceResource.
> Specless components in libraries don't get their assets properly resolved
> -------------------------------------------------------------------------
>
> Key: TAPESTRY-1396
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1396
> Project: Tapestry
> Issue Type: Bug
> Components: Framework
> Affects Versions: 4.1.1
> Reporter: Marcus Schulte
> Assigned To: Jesse Kuhnert
> Fix For: 4.1.2
>
>
> We are trying to move a little library of ours to Java-5 with full usage of annotations, without jwc-files. While a component itself is recognised this way. Asset-resolution relative to the (non-existing) specification doesn't work.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org