Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
WFLY-7618: fix code not to use default platform dependant encoding

  1. … 104 more files in changeset.
WFLY-7298 Testsuite IO ops housekeeping

- don't always log deployments

- remove full tree read that is not used

- replace system.out --> log.trace

- replace log.info --> log.trace

- make all test code use jboss logging instead of 3 diffrent log frameworks

  1. … 531 more files in changeset.
WFLY-6901 - enable checkstyle for manualmode testsuite

    • -38
    • +38
    ./ReloadRequiringChangesTestCase.java
    • -30
    • +30
    ./WSAttributesChangesTestCase.java
  1. … 17 more files in changeset.
[WFLY-6409]: Update default domain configuration to use remote+http

Updating default domain configurations.

Removing usage of deprecated http-remotting

  1. … 44 more files in changeset.
Use the solid reload method in ReloadWSDLPublisherTestCase

  1. … 1 more file in changeset.
WFLY-4732 wait for server to reload after test case

    • -53
    • +3
    ./ReloadRequiringChangesTestCase.java
  1. … 2 more files in changeset.
WFLY-4732 wait for server to reload after test case

    • -53
    • +3
    ./ReloadRequiringChangesTestCase.java
  1. … 2 more files in changeset.
Testsuite calls to low-level reload ops should deal with CancellationException as it can happen if the channel gets closed

    • -12
    • +11
    ./ReloadRequiringChangesTestCase.java
  1. … 3 more files in changeset.
[WFLY-3790] Upgrade WS stack

    • -3
    • +194
    ./WSAttributesChangesTestCase.java
  1. … 62 more files in changeset.
WFLY-3007 : All calls to InetAddress.getHostName() are wrapped in NetworkUtils to canonize IPv6 addresses.

  1. … 15 more files in changeset.
WFLY-2618 : Intermittent 'AssertionError: expected:<200> but was:<500>' in org.jboss.as.test.manualmode.ws.ReloadWSDLPublisherTestCase.testHelloStringAfterReload The test was failing intermittently because per default the JVM is using HttpConnection with keep-alive and a timeout of 5s. By setting the keep-alive to false in the setup and setting it to the value before the test on tear down we ensure a more stable test.

[WFLY-2451] Adding unit test + some formatting / indentation fixes

    • -25
    • +25
    ./WSAttributesChangesTestCase.java
  1. … 2 more files in changeset.
[WFLY-2451] Adding unit test + some formatting / indentation fixes

    • -25
    • +25
    ./WSAttributesChangesTestCase.java
  1. … 2 more files in changeset.
[WFLY-2451] Adding integration testcase

    • -0
    • +301
    ./WSAttributesChangesTestCase.java
[WFLY-2451] Adding integration testcase

    • -0
    • +301
    ./WSAttributesChangesTestCase.java
[WFLY-1759] Fixing testcase to restore original wsdl-host value

    • -8
    • +37
    ./ReloadRequiringChangesTestCase.java
[WFLY-1759] Adding a testcase

    • -0
    • +272
    ./ReloadRequiringChangesTestCase.java
'running-mode' is a bad way to verify the server restart. It can be "NORMAL" while the server is still starting, causing the connection attempt in checkWsdl() to fail.

Properly handle client-side of low level reload op in ReloadWSDLPublisherTestCase

WFLY-1754 : Adding a test to confirm the current bug JBWS-3671 which relates to WFLY-1754. The test tries to reload the server and the WSDL is still accessible.

    • -0
    • +34
    ./EndpointIface.java
    • -0
    • +163
    ./ReloadWSDLPublisherTestCase.java