You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ta...@jakarta.apache.org> on 2005/09/16 16:10:55 UTC
[jira] Assigned: (TAPESTRY-349) Search path for managed bean classes
[ http://issues.apache.org/jira/browse/TAPESTRY-349?page=all ]
Howard M. Lewis Ship reassigned TAPESTRY-349:
---------------------------------------------
Assign To: Howard M. Lewis Ship
> Search path for managed bean classes
> ------------------------------------
>
> Key: TAPESTRY-349
> URL: http://issues.apache.org/jira/browse/TAPESTRY-349
> Project: Tapestry
> Type: Improvement
> Components: Framework
> Versions: 4.0
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Priority: Minor
>
> Already, there is meta data to control what packages are searched for component classes and page classes. It would be nice if it was possible (within a page/component specification, and inside a namespace specifsication) to define a list of packages to earch for managed beans. This would reduce the "density" of the XML.
--
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: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org