> I've been working lately with Castor and its SourceGenerator. My current
> project has to do with reconfiguring and repackaging (splitting) big EARs
> into pieces with different configs.
>
> SourceGenerator was the quickest way for me to get started, without having
> to learn anything about parsing XML. They Castor framework also has a
> mapping framework that allows one to map your custom object hierarchy to
> XML by just writing a schema. Perhaps, this is a way to go.
I have not used Castor, though I have been tempted several times. If Castor
can take an XML stream and turn it into an object, that would be great for
most if not all the configuration uses of it. Each configurable component
could define a Configuration object, which would be generated by Castor
(hopefully taking into account the whitespace issue that I mentioned before,
or provide some way to customize that).
Then the application can go on with its life pulling configuration from the
config object instead of dealing with the XML api.
Since you are more familar with Castor, perhaps you can common on how
functional a design like this might be (including pitfals and such).
> I was also wondering if someone would rewrite JBoss dtds into XML schemas
> and maintain them. Schemas are much more expressive. I did hack a
> translation from jboss dtd to schema, there are tools to do that as well,
> but it would, probably be good if JBoss community had official XML Schemas
> for its config XMLs.
I know jack about XML schemas. Personally I like XML, but I do not want it
to get in my way, which is why I would like an XML -> Object for
configuration. Any ways, sounds like a good idea to me. Why don't you tack
a wack at the schemas?
--jason
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
