[jira] [Commented] (TAP5-1649) ComponentClassResolver should allow "common package root name" of a single term, and not require two terms

["Hudson (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TAP5-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13104223#comment-13104223 ] 

Hudson commented on TAP5-1649:
------------------------------

Integrated in tapestry-trunk-freestyle #518 (See [https://builds.apache.org/job/tapestry-trunk-freestyle/518/])
    TAP5-1649: Allow mapping of classpath asset aliases to a package name of even just a single term

hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1170400
Files : 
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/ComponentClassResolverImpl.java
* /tapestry/tapestry5/trunk/tapestry-core/src/test/java/org/apache/tapestry5/internal/services/ComponentClassResolverImplTest.java


> ComponentClassResolver should allow "common package root name" of a single term, and not require two terms
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1649
>                 URL: https://issues.apache.org/jira/browse/TAP5-1649
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.3, 5.2
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>             Fix For: 5.3
>
>
> Currently, if a single folder has multiple packages, ComponentClassResolver looks for a common package name to use when constructing classpath asset URLs, for example, using:
> LibraryMapping("foo", "com.foo.bar")
> LibraryMapping("foo", "com.foo.bazz")
> The common root package would be "com.foo", and asset URLs would be /assets/xxxx/foo/bar/abc.png or /assets/xxxx/foo/bazz/xyz.pdf
> In other work, /assets/xxxx/foo maps to "com/foo" on the classpath, and the remainder is mapped in.
> However, for some clients, requiring two folders is overkill, and reducing this limit to a single folder is desirable.
> Reducing down to no folders is problematic, since it makes the entire classpath visible to browsers, including important resources such as hibernate.cfg.xml and the like.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira