<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 06/01/2016 04:16 AM, Alessio Soldano
wrote:<br>
</div>
<blockquote cite="mid:574E99F6.6080808@redhat.com" type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<div class="moz-cite-prefix">Il 01/06/2016 03:14, Ron Sigal ha
scritto:<br>
</div>
<blockquote
cite="mid:2f4e5535-5266-3897-e96c-5ab51d814fab@redhat.com"
type="cite">
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
<p>Hi guys,</p>
<p>After slogging through as many bug JIRAs as possible for
3.0.17.Final, I felt like I needed to do something different
for a while, so I started looking at non-blocking IO for
JAX-RS 2.1. One of the issues I ran into is the servlet
version problem. Even though resteasy-jaxrs declares a
dependency on servlet 3.1, its dependency on tjws brings in
servlet 2.5, which gets in the way of using servlet 3.1. I've
done some refactoring:</p>
<p> 1) moved everything related to tjws from resteasy-jaxrs to
tjws</p>
<p> 2) moved all tests (except i18n tests) from resteasy-jaxrs
to resteasy-jaxrs-testsuite (so resteasy-jaxrs doesn't depend
on tjws)<br>
</p>
<p> 3) removed the dependency of resteasy-jaxrs on tjws<br>
</p>
<p> 4) created a dependency of tjws on resteasy-jaxrs</p>
<p>I thought I'd ask for comments before I create a pull
request. Two points come to mind:</p>
<p>1) Originally, resteasy-jaxrs-testsuite was created to hold
tests specifically related to JAX-RS 2.0 (hence the nextgen
packages). The plan was to upgrade all of the old tests to use
JAX-RS 2.0 stuff like the new client framework, but it never
happened. This might be a good time to do that.<br>
</p>
</blockquote>
+1, we should try to get rid of all those warnings about old
client stuff in the build. And given we're working on a new minor
and that stuff was deprecated in 3.0.x, we could actually think
about removing the old client framework.<br>
</blockquote>
<br>
Given that we have some large pieces pieces ready to deprecate (old
client framework, TJWS, old validation (see my previous note on
mailing list), maybe we should do a 3.0.18.Final release in which
all this stuff is deprecated so that we can start 3.1.0.Final with a
clean slate. Just a thought.<br>
<br>
<blockquote cite="mid:574E99F6.6080808@redhat.com" type="cite"> <br>
<br>
<blockquote
cite="mid:2f4e5535-5266-3897-e96c-5ab51d814fab@redhat.com"
type="cite">
<p> </p>
<p>2) I know we've talked about what to do with tjws, but I
don't know if we reached a conclusion. This would be a good
time to deprecate it, if we're going to do that.</p>
</blockquote>
+1, sure.<br>
<br>
I'd be glad to review your PR on this. It should be the first step
to revisiting the testsuite to default to using WFLY as container.<br>
</blockquote>
<br>
I created RESTEASY-1410 "Segregate TJWS from resteasy-jaxrs" and PR
<a class="moz-txt-link-freetext" href="https://github.com/resteasy/Resteasy/pull/821">https://github.com/resteasy/Resteasy/pull/821</a>. Since you agree that
we should deprecate TJWS, I'll do one more commit in which all of
the TJWS classes are @deprecated.<br>
<br>
<blockquote cite="mid:574E99F6.6080808@redhat.com" type="cite"> <br>
Thanks<br>
Alessio<br>
<br>
<pre class="moz-signature" cols="72">--
Alessio Soldano
Web Service Lead, JBoss</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
resteasy-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:resteasy-dev@lists.jboss.org">resteasy-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/resteasy-dev">https://lists.jboss.org/mailman/listinfo/resteasy-dev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
My company's smarter than your company (unless you work for Red Hat)</pre>
</body>
</html>