Uploaded image for project: 'Arquillian'
  1. Arquillian
  2. ARQ-2115

Create Arquillian adapter for WebSphere 9

XMLWordPrintable

      Hi, guys,

      I have created the Arquillian adapter for WebSphere 9. Here is the summary of the PR [1]:

      #### Short description of what this resolves:
      Hi, guys,

      my name is Marian Macik and I work at Red Hat as QE Engineer on jBPM project. This PR introduces Arquillian container adapter for WebSphere 9. We have been using it at Red Hat in our QE automation for about two months without any issues. It is copied from adapter for WebSphere 8.5 (as WebSphere 8.5 was copied from WebSphere 8). There were only some minor changes when it comes to system paths pointing at WebSphere dependencies (jgss-provider and ws-admin-client).

      However, since WebSphere 9, wsadmin is using jython27 by default. Jython21 is still supported and to use jython21, 'com.ibm.ws.admin.client.forJython21_9.0.jar' should be used. Moreover, the new wsadmin jar has additional libraries which are not used by Arquillian (such as Python JSR 223 implementation) and might cause issues when deploying and running tests. If this happens, simply override this property with jython21 jar:

      -Dws_admin_client_jar_name=com.ibm.ws.admin.client.forJython21_9.0.jar

      I added this property because the new jython27 wsadmin implementation was causing issues since it loaded unwanted classes on the classpath. Of course, by default the new jython27 wsadmin is used, override is optional.

      I have also run the enclosed tests with my own arquillian.xml and they have passed.

      Thanks,

      Marian

      [1] https://github.com/arquillian/arquillian-container-was/pull/29

            [ARQ-2115] Create Arquillian adapter for WebSphere 9

            Gerhard Poul (Inactive) added a comment -

            Yes, bartosz-1 is correct. That is the current situation. I've had a discussion with someone from IBM last week and we'll see whether this can be changed or not; if you're a licensed customer you're certainly more than welcome to point IBM development or your IBM account reps in my direction as well to get this pushed in the right direction, if this is important for you.

            Gerhard Poul (Inactive) added a comment - Yes, bartosz-1 is correct. That is the current situation. I've had a discussion with someone from IBM last week and we'll see whether this can be changed or not; if you're a licensed customer you're certainly more than welcome to point IBM development or your IBM account reps in my direction as well to get this pushed in the right direction, if this is important for you.

            Bartosz Majsak added a comment -

            AFAIK the only one we can officially release to Maven Central is based on open source Liberty Profile. The others you have to build yourself if you have WAS licensed.

            Maybe gpoul_jira can correct me if I'm wrong.

            Bartosz Majsak added a comment - AFAIK the only one we can officially release to Maven Central is based on open source Liberty Profile. The others you have to build yourself if you have WAS licensed. Maybe gpoul_jira can correct me if I'm wrong.

            Marian Macik added a comment - - edited

            Hi, bartosz-1,

            does it mean that WebSphere adapter has finally been released and deployed to the Maven repo?

            Marian Macik added a comment - - edited Hi, bartosz-1 , does it mean that WebSphere adapter has finally been released and deployed to the Maven repo?

              gpoul_jira Gerhard Poul (Inactive)
              mmacik@redhat.com Marian Macik
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: