[
https://issues.apache.org/jira/browse/TAPESTRY-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12566452#action_12566452
]
Jim Roycroft commented on TAPESTRY-1661:
----------------------------------------
Thanks Jesse. This helps clean up my component class files a lot. Now I don't
have to use this ugly hack in them anymore!
<hack>
@Asset("context:/somepage.html")
public abstract IAsset get$template();
</hack>
> Specless component html template needs a package based resolution strategy
> --------------------------------------------------------------------------
>
> Key: TAPESTRY-1661
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1661
> Project: Tapestry
> Issue Type: Improvement
> Components: Framework
> Affects Versions: 4.1.2
> Environment: any
> Reporter: Jesse Kuhnert
> Assignee: Jesse Kuhnert
> Fix For: 4.1.3
>
>
> When creating a specless component the html templates won't be resolved
> unless they are relative to the classpath location of the component class.
> It should be easy enough to take the class package string and break it up and
> search the context path using that as a last resort.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
