<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi all,<br>
<br>
I've probably missed the final decision about that. I've worked on
2 issues last week:<br>
<br>
- WFLY-4566 Remove support for jboss-as-datasources_1_0.xsd<br>
- WFLY-4568 Remove support for jboss-as-resource-adapters_1_0.xsd
<br>
<br>
removing very old xsds. I have a lot of tests failing because we
still support 7.x xsds. <br>
I would suggest to reopen this discussion and evaluate if and when
we are de-supporting them.<br>
<br>
I'm sorry if a decision was already taken and I've missed or
misunderstood that one<br>
<br>
regards<br>
S.<br>
<br>
<br>
On 03/27/2015 12:13 AM, Tomaž Cerar wrote:<br>
</div>
<blockquote
cite="mid:CAMquZP4kGzBv+jy_f_P3nmVv=tPXwFFGwbWOzkpAa=vaPJdY0Q@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>Hi folks,<br>
<br>
</div>
we discussed on team meeting in Brno
about dropping support for old legacy
host controllers<br>
</div>
when running in mixed domain mode (having
DC of newer version managing older version
HCs)<br>
<br>
</div>
We also discussed dropping old xsd sachems
& parsers as it would help us cleanup
and simplify code<br>
</div>
in many subsystems as there are cases where we
support and maintain 5 and more different <br>
versions of parser. For example currently web
subsystem has 8, infinispan 7, ejb &
jackorb have 6, ...<br>
</div>
<div>We still have parsers that that ware
shipped back in 7.0.0 and became obsolete in
later 7.0.x releases.<br>
</div>
<div><br>
Given that we decided that we are dropping
support for running mixed domain mode for host
controller<br>
</div>
</div>
that are older than 7.3.0 (EAP 6.2) as is tracked
by <a moz-do-not-send="true"
href="https://issues.jboss.org/browse/WFLY-3564">https://issues.jboss.org/browse/WFLY-3564</a><br>
</div>
<br>
I would also like to suggest that we do the same for
xml schemas & parsers.<br>
<br>
</div>
<b>What is the downside?</b><br>
</div>
<br>
Automatic upgrading from JBoss AS 7.1.x/EAP < 6.2
version with using same standalone.xml won't work
anymore.<br>
</div>
User would need to upgrade to WildFly 8.x and from there
to 9 or 10 (depending when we drop this)<br>
</div>
Because of replacement of web subsystem with undertow and
introduction of few other subsystems (io, SM)<br>
</div>
this already doesn't work for 7.x-->8+, but we do have
plans how to improve that.<br>
<br>
<br>
</div>
<div>So, are there any objections against this?<br>
</div>
<div><br>
--<br>
</div>
<div>Tomaž<br>
</div>
<div><br>
<br>
</div>
<br>
<div>
<div>
<div>
<div>
<div>
<div>
<div><br>
<div>
<div>
<div>
<div>
<div><br>
<br>
<br>
<div>
<div><br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
wildfly-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/wildfly-dev">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a></pre>
</blockquote>
<br>
</body>
</html>