On 2 Apr 2012, at 09:29, Jeff Mesnil wrote:
Hi,
I am working on a JIRA issue to add missing configuration parameters to
messaging resources[1]
I did a quick patch to unblock the performance teams but I am revisiting
it to fix it properly[2].
As I am changing the XSD schema, I need to bump up its version.
My changes are small (I'm just adding elements) but I wonder what the
policy to manage schema changes is.
* should I be able to read any previous configuration version? or only
the last 2?
Old versions of the schema should be readable and converted into
whatever ops your subsystem currently takes
* if I am reading an old configuration version, should I persist it
at
the same old version or the latest version?
We persist as the latest version
I looked at ejb3 subsystem to see how configuration schemas are handled.
Is it a good candidate to copy?
thanks,
jeff
[1]
https://issues.jboss.org/browse/AS7-4330
[2]
https://github.com/jmesnil/jboss-as/commit/2f4389a10fe61bd054a5e4729ae8c6...
--
Jeff Mesnil
JBoss, a division of Red Hat
http://jmesnil.net/
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev