[wildfly-dev] What is the best practice for back porting subsystem model changes

[Brian Stansberry]

Did this bit of configuration exist in the previous xsd and the parser 
for that version was just wrong? If not, then you create a new xsd 
version and a parser for that and any intermediate parsers don't need to 
be updated.

I'm not sure why backporting like this would need to happen though. I'll 
ping you offline for details.


On 3/21/16 11:42 AM, Michael Musgrove wrote:
> What is the recommended approach to back porting model changes. The
> context for the question is that we have added a bit of configuration to
> narayana and exposed it in the subsystem model as an attribute on an
> existing element. The latest subsystem version has more parser versions
> than the target version we need to back port to. Since we do not want to
> back port each intermediate parser, how do we get the new attribute into
> the earlier version?
>
> --
> Michael Musgrove
> Transactions Team
> e: mmusgrov at redhat.com <mailto:mmusgrov at redhat.com>
> t: +44 191 243 0870
>
> Registered in England and Wales under Company Registration No. 03798903
> Directors: Michael Cunningham (US), Paul Hickey (Ireland), Matt Parson
> (US), Charles Peters (US)
>
> Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Michael
> O'Neill(Ireland)
>
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>


-- 
Brian Stansberry
Senior Principal Software Engineer
JBoss by Red Hat