You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hivemind.apache.org by "Achim Hügen (JIRA)" <hi...@jakarta.apache.org> on 2005/08/10 17:23:50 UTC

[jira] Resolved: (HIVEMIND-140) may separate configuration-point and configuration schema so configuration-point provide config data and define config-schema and eliminate the using of contribution element in configuration

     [ http://issues.apache.org/jira/browse/HIVEMIND-140?page=all ]
     
Achim Hügen resolved HIVEMIND-140:
----------------------------------

    Resolution: Invalid

This is already possible and uses almost the same syntax you suggested (schema-id instead of schema):
http://jakarta.apache.org/hivemind/descriptor.html#configuration-point.

> may  separate configuration-point and configuration schema so configuration-point provide config data and <schema> define config-schema and eliminate the using of contribution element in configuration
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>          Key: HIVEMIND-140
>          URL: http://issues.apache.org/jira/browse/HIVEMIND-140
>      Project: HiveMind
>         Type: Improvement
>   Components: framework
>     Versions: 1.1
>     Reporter: wu zhi hui

>
> I think  that the using of current service configuration is a little complex ,think about the following example
> 1. define configuration data schema
> <configuration-point id="mail_source_config_2">
>   <schema>
>     <element name="mail-source">
>     <attribute name="host" required="true"/>
>   <attribute name="user" required="true"/> 
>    <conversion class="hellow.MailSource">
>     <map attribute="host" property="host" />
>     <map attribute="user" property="user"/>
>   </conversion>
>   </element>
>   </schema>
> </configuration-point>
> 2.define the configuration data
> <contribution configuration-id="mail_source_config_2">
>   <mail-source host="host1" user="user1"/>
> </contribution>
>  </module>
> 3. reference the contribution (why not configuration-point ?) to service config property
> <set-configuration property="config" configuration-id="april2.schemas.mail_source_config_2"/>
>  in this way ,I can't reuse the configuration schema ,because <contribution> element no Id
>  I surgest that it can changed like the following :
> 1. define configuration schema
>  <schema id="mail_source_config_2_schema">
>     <element name="mail-source">
>     <attribute name="host" required="true"/>
>   <attribute name="user" required="true"/> 
>    <conversion class="hellow.MailSource">
>     <map attribute="host" property="host" />
>     <map attribute="user" property="user"/>
>   </conversion>
>   </element>
>   </schema>
> 2. define the configuration data
> <configuration-point id="mail_source_config_2" schema="mail_source_config_2_schema"">
>  <mail-source host="host1" user="user1"/>
> </configuration-point>
>  
> thanks.

-- 
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: hivemind-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: hivemind-dev-help@jakarta.apache.org