[
https://issues.apache.org/jira/browse/TAPESTRY-919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Kuhnert updated TAPESTRY-919:
-----------------------------------
Fix Version/s: (was: 4.1.3)
4.1.4
> Include a component-class and a page-class in the library and application
> specification DTDs
> --------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-919
> URL: https://issues.apache.org/jira/browse/TAPESTRY-919
> Project: Tapestry
> Issue Type: Improvement
> Components: Framework
> Affects Versions: 4.0.2
> Reporter: Leonardo Quijano Vincenzi
> Priority: Minor
> Fix For: 4.1.4
>
>
> This could be a useful shortcut for those of us that use annotations, but for
> some reason can't specify a single page class search path. The library and
> application specification DTDs include the <component-type> and the <page> to
> allow the developer to set a specification file for a component or page.
> If the developer is using annotations instead of specification files, he has
> no choice other than to do one of the following:
> a) Create an empty specification file for the component.
> b) Define a set of "directory classes" for pages in the
> org.apache.tapestry.page-class-packages variable.
> Now,
> (a) has the drawback of forcing the developer to include an empty file
> (clutter) for every page or component he develops.
> (b) has the drawback that it's very imprecise, specially for components.
> Sometimes the developer already know the specific component class he's using
> (and he could even want to leverage the refactoring help that IDEs like
> Eclipse provide), and specifying a "search path" is cumbersome at best.
> Then, my idea is to add an optional "component-class" and "page-class"
> attribute to the "component-type" and "page" elements, as this:
> <component-type type="SomeComponent" component-class="foo.bar.SomeComponent"
> />
> or
> <page name="SomePage" page-class="foo.bar.SomePage" />
--
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]
