<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p>Hmmm, I didn't know that existed. <br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 04/19/2017 10:51 AM, Tomaž Cerar
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAMquZP4BL1CB1dy-qD3++Na-kfTs4KC5bzeo0b_tij2hW=GmmQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>Maybe solution would be to use undertow arquillian adapter
          <a moz-do-not-send="true"
href="http://arquillian.org/modules/undertow-embedded-container-adapter/">http://arquillian.org/modules/undertow-embedded-container-adapter/</a><br>
        </div>
        to test again undertow?<br>
      </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On Wed, Apr 19, 2017 at 4:27 PM, Ron
          Sigal <span dir="ltr">&lt;<a moz-do-not-send="true"
              href="mailto:rsigal@redhat.com" target="_blank">rsigal@redhat.com</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div bgcolor="#FFFFFF" text="#000000"><span class="">
                <p>On 04/19/2017 06:32 AM, Katerina Novotna wrote:<br>
                </p>
                <blockquote type="cite">
                  <pre>----- Original Message -----
</pre>
                  <blockquote type="cite">
                    <pre>This question arises from RESTEASY-1617 "Add support for injection in
constraint validators on Java SE". We already use a CDI aware
ValidatorFactory in the context of Wildfly / EAP, but not in Java SE.

My question is: where do I test this new facility? I've got a test that
makes an invocation to an embedded instance of Undertow. We have
</pre>
                  </blockquote>
                  <pre>Could you please point me to your branch with the test?</pre>
                </blockquote>
                <br>
              </span> The branch is at <a moz-do-not-send="true"
                class="m_3971008575538606151moz-txt-link-freetext"
                href="https://github.com/ronsigal/Resteasy/tree/1617"
                target="_blank">https://github.com/ronsigal/<wbr>Resteasy/tree/1617</a>.
              The test, temporarily, is at
              <a moz-do-not-send="true"
                class="m_3971008575538606151moz-txt-link-freetext"
href="https://github.com/ronsigal/Resteasy/blob/1617/testsuite/integration-tests/src/test/java/org/jboss/resteasy/experiment/undertow/Test1617.java"
                target="_blank">https://github.com/ronsigal/<wbr>Resteasy/blob/1617/testsuite/<wbr>integration-tests/src/test/<wbr>java/org/jboss/resteasy/<wbr>experiment/undertow/Test1617.<wbr>java</a>.
              <br>
              <br>
              I have a lot of tests (in my local branches) in
              integration-tests/src/test/<wbr>java/org/jboss/resteasy/<wbr>experiment/undertow,
              by the way. I usually start with an embedded undertow
              server while I'm still investigating or testing.<span
                class=""><br>
                <br>
                <blockquote type="cite">
                  <blockquote type="cite">
                    <pre>resteasy-integration-tests for running tests on Wildfly, which isn't
appropriate in this case. We also have resteasy-unit-tests, but my
understanding is that it's not for tests that make network invocations.

We could create a new test module for running tests with embedded
servers. Or I could just put it in resteasy-integration-tests and forget
about it.

It's not a big deal, but I'm open to suggestions.
</pre>
                  </blockquote>
                  <pre>My opinion is, that it could be placed into resteasy-integration-tests into new package to separate the tests from other integration tests.</pre>
                </blockquote>
                <br>
              </span> So, maybe,
              .../testsuite/integration-<wbr>tests/src/test/java/org/jboss/<wbr>resteasy/undertow
              ?<span class=""><br>
                <br>
                <blockquote type="cite">
                  <pre>If in the future there should be more tests for different server adapters, then new module would be better.</pre>
                </blockquote>
                <br>
              </span> Well, that's an interesting issue. I see that
              resteasy-undertow, resteasy-netty, and resteasy-netty4,
              for example, have a src/test/java directory. I haven't
              looked too closely, but I suppose those tests are
              specifically for issues related to the particular server
              adaptors. In the case of my test for RESTEASY-1617, on the
              other hand, I just want to run with <b>some</b> server
              outside of Wildfly; that is, I want to run the test with
              Java SE. <br>
              <br>
              So, I think the question is, how often does Resteasy
              behavior potentially differ when running with Java SE
              compared to running with JEE? I don't have a good answer,
              off the top of my head. I guess at least one relevant
              situation would be when there are different dependencies
              for Java SE and JEE. Note that in this case, I added<br>
              <br>
              <blockquote>
                <blockquote type="cite">&lt;dependency&gt;<br>
                      &lt;groupId&gt;org.hibernate&lt;/<wbr>groupId&gt;<br>
                      &lt;artifactId&gt;hibernate-<wbr>validator-cdi&lt;/artifactId&gt;<br>
                      &lt;version&gt;5.4.1.Final&lt;/version&gt;<br>
                  &lt;/dependency&gt;<br>
                  <br>
                  &lt;dependency&gt;<br>
                      &lt;groupId&gt;<a moz-do-not-send="true"
                    href="http://org.jboss.weld.se" target="_blank">org.jboss.weld.se</a>&lt;/<wbr>groupId&gt;<br>
                      &lt;artifactId&gt;weld-se&lt;/<wbr>artifactId&gt;<br>
                      &lt;version&gt;2.4.3.Final&lt;/version&gt;<br>
                  &lt;/dependency&gt;</blockquote>
              </blockquote>
              <br>
              to pom.xml in resteasy-integration-tests. Note that <a
                moz-do-not-send="true" href="http://org.jboss.weld.se"
                target="_blank">org.jboss.weld.se</a> doesn't exist in
              Wildfly. So, how common is that?<br>
              <br>
              <br>
              <blockquote type="cite">
                <pre>-- Katka
</pre>
              </blockquote>
              <span class=""> <br>
                <pre class="m_3971008575538606151moz-signature" cols="72">-- 
My company's smarter than your company (unless you work for Red Hat)</pre>
              </span></div>
            <br>
            ______________________________<wbr>_________________<br>
            resteasy-dev mailing list<br>
            <a moz-do-not-send="true"
              href="mailto:resteasy-dev@lists.jboss.org">resteasy-dev@lists.jboss.org</a><br>
            <a moz-do-not-send="true"
              href="https://lists.jboss.org/mailman/listinfo/resteasy-dev"
              rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/resteasy-dev</a><br>
            <br>
          </blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
My company's smarter than your company (unless you work for Red Hat)</pre>
  </body>
</html>