Hmm, I didn't understand your proposol fully. And I
also didn't look at the details of jaxe, so I cannto tell where jaxe could help
me. My normal way to launch such projects, is to use a prototyping until I have
a base framework that I will work on. Until then I dont want to use too many
frameworks, because it complicates matters.
My first step was to write some extensions to the
hivemind registry builder and registry infrastructure, so I can expose all
configuration points and service points (normally you cannot access those
information, and for the information you get, you need the ids). From there I
will try to construct some wizards when adding new contributions and even
services... I will see where this will take me.
Greetings,
Christian.
I think it would be possible to create an xsl to manage an xsd and generate a jaxe configuration file, at least we could generate a configuration file using hivemind injection, so with no need of xsl. I think the last solution thought requiring more java code would be more useful to us.
Von: Andrea Chiumenti [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 28. Februar 2006 13:02
An: [email protected]
Betreff: Re: Hivemind Module Editor
I mean: use a service where we have contributed our schemas and then make it to generate the configuration file.
Do you like the idea ?
