You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hivemind.apache.org by hi...@jakarta.apache.org on 2004/10/19 16:15:51 UTC
[jira] Created: (HIVEMIND-70) Schema extension capability
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/HIVEMIND-70
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HIVEMIND-70
Summary: Schema extension capability
Type: Improvement
Status: Unassigned
Priority: Major
Project: HiveMind
Components:
framework
Assignee:
Reporter: Jean-Francois Poilpret
Created: Tue, 19 Oct 2004 7:15 AM
Updated: Tue, 19 Oct 2004 7:15 AM
Description:
It would be interesting, in hivemind module description files, to be able to define a schema (or parameter-schema) in terms of another existing schema.
For instance, something like:
<schema id="A">
<element name="a1">
...
</element>
<element name="a2">
...
</element>
</schema>
<schema id="B">
<sub-schema id="A"/>
<element name="b1">
...
</element>
</schema>
Then the second schema should be logically identical as the following declaration:
<schema id="B">
<element name="a1">
...
</element>
<element name="a2">
...
</element>
<element name="b1">
...
</element>
</schema>
Such a mechanism would enable reuse of pre-defined Hivemind schemas (in particular I think about the schema used by BuilderFactory: I think many people here already got the need to create a new Factory service that would "extend" the current BuilderFactory. It is possible currently, but the major problem with this is that we need to copy/paste the schema defined for BuilderFactory into our own configuration file. In addition, any changes to the BuilderFactory schema in a newer version of Hivemind obliges the developer to update his own schema, by copy/pasting once again (for every new version of Hivemind)).
---------------------------------------------------------------------
JIRA INFORMATION:
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: hivemind-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: hivemind-dev-help@jakarta.apache.org
[jira] Commented: (HIVEMIND-70) Schema extension capability
Posted by "Davor Hrg (JIRA)" <hi...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/HIVEMIND-70?page=comments#action_12320267 ]
Davor Hrg commented on HIVEMIND-70:
-----------------------------------
Just to say, the recursive <element> and schema reuse is something I need badly. I'm just a beginner with Hivemind, like it a lot, hope this gets resolved soon. I know howard is busy enough with tapestry....
> Schema extension capability
> ---------------------------
>
> Key: HIVEMIND-70
> URL: http://issues.apache.org/jira/browse/HIVEMIND-70
> Project: HiveMind
> Type: Improvement
> Components: framework
> Reporter: Jean-Francois Poilpret
>
> It would be interesting, in hivemind module description files, to be able to define a schema (or parameter-schema) in terms of another existing schema.
> For instance, something like:
> <schema id="A">
> <element name="a1">
> ...
> </element>
> <element name="a2">
> ...
> </element>
> </schema>
> <schema id="B">
> <sub-schema id="A"/>
> <element name="b1">
> ...
> </element>
> </schema>
> Then the second schema should be logically identical as the following declaration:
> <schema id="B">
> <element name="a1">
> ...
> </element>
> <element name="a2">
> ...
> </element>
> <element name="b1">
> ...
> </element>
> </schema>
> Such a mechanism would enable reuse of pre-defined Hivemind schemas (in particular I think about the schema used by BuilderFactory: I think many people here already got the need to create a new Factory service that would "extend" the current BuilderFactory. It is possible currently, but the major problem with this is that we need to copy/paste the schema defined for BuilderFactory into our own configuration file. In addition, any changes to the BuilderFactory schema in a newer version of Hivemind obliges the developer to update his own schema, by copy/pasting once again (for every new version of Hivemind)).
--
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