You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Nanda Firdausi (JIRA)" <ta...@jakarta.apache.org> on 2005/03/23 07:02:20 UTC
[jira] Created: (TAPESTRY-287) Improvement of registry builder
Improvement of registry builder
-------------------------------
Key: TAPESTRY-287
URL: http://issues.apache.org/jira/browse/TAPESTRY-287
Project: Tapestry
Type: Improvement
Components: Framework
Versions: 3.1
Reporter: Nanda Firdausi
Priority: Minor
Today's 3.1 registry builder will search for WEB-INF/hivemodule.xml and WEB-INF/applicationName/hivemodule.xml, I would like to request a search for hivemodule.xml corresponding to a library. It can be implicit (where the library specification located or explicit).
This is important so that library developers can create Out-Of-The-Box solutions without having users write their own entry in the hivemodule.xml.
I refer to conversation in Mailing List that Component availability is important to Tapestry. But component availability must be followed by pluggable addition of library to Tapestry (just copy the jar and add 1 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
[jira] Resolved: (TAPESTRY-287) Improvement of registry builder
Posted by "Howard M. Lewis Ship (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-287?page=history ]
Howard M. Lewis Ship resolved TAPESTRY-287:
-------------------------------------------
Resolution: Invalid
Each library will be packaged in a JAR and the deafult HiveMind RegistyrBuidler will pick up META-INF/hivemodule.xml from each JAR on the classpath.
> Improvement of registry builder
> -------------------------------
>
> Key: TAPESTRY-287
> URL: http://issues.apache.org/jira/browse/TAPESTRY-287
> Project: Tapestry
> Type: Improvement
> Components: Framework
> Versions: 3.1
> Reporter: Nanda Firdausi
> Priority: Minor
>
> Today's 3.1 registry builder will search for WEB-INF/hivemodule.xml and WEB-INF/applicationName/hivemodule.xml, I would like to request a search for hivemodule.xml corresponding to a library. It can be implicit (where the library specification located or explicit).
> This is important so that library developers can create Out-Of-The-Box solutions without having users write their own entry in the hivemodule.xml.
> I refer to conversation in Mailing List that Component availability is important to Tapestry. But component availability must be followed by pluggable addition of library to Tapestry (just copy the jar and add 1 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