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/03/24 14:23:20 UTC
[jira] Resolved: (TAPESTRY-288) Improvement of registry builder
[ http://issues.apache.org/jira/browse/TAPESTRY-288?page=history ]
Howard M. Lewis Ship resolved TAPESTRY-288:
-------------------------------------------
Resolution: Invalid
Fix Version: 3.1
Libaries can package their HiveMind module descriptor as META-INF/hivemodule.xml and it will be picked up by the standard (HiveMind) mechanism.
> Improvement of registry builder
> -------------------------------
>
> Key: TAPESTRY-288
> URL: http://issues.apache.org/jira/browse/TAPESTRY-288
> Project: Tapestry
> Type: Improvement
> Components: Framework
> Versions: 3.1
> Reporter: Nanda Firdausi
> Fix For: 3.1
>
> Today's Tapestry31 registry builder automatically read WEB-INF/hivemodule.xml and WEB-INF/applicationName/hivemodule.xml.
> For the easiness of deploying library, it's better if library can also contribute to the whole registry, by giving algorithm that read hivemodule.xml for each library, either implicitly (in the same dir as library specification) or explicitly.
> This way, library developers can deliver theirs library Out-Of-The-Box, without having user writing many things in their hivemodule.xml.
> To add library, user only need exactly two steps:
> 1. Add the jar to classpath
> 2. Add one line in application specification
--
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
-
If you want more information on JIRA, or have a bug to report 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