Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 900452 (JBPAPP6-796)

Summary:

Unable to run WS performance tests, missing dependencies for jbossws-cxf-client in maven repo zip

Product:

[JBoss] JBoss Enterprise Application Platform 6

Reporter:

Rostislav Svoboda <rsvoboda>

Component:

Build, Web Services

Assignee:

Paul Gier <pgier>

Status:

CLOSED NEXTRELEASE

QA Contact:

Severity:

urgent

Docs Contact:

Priority:

urgent

Version:

6.0.0

CC:

asoldano, cdewolf, pgier, rajesh.rajasekaran, ropalka, rsvoboda, smcgowan

Target Milestone:

---

Target Release:

EAP 6.0.0

Hardware:

Unspecified

OS:

Unspecified

URL:

http://jira.jboss.org/jira/browse/JBPAPP6-796

Whiteboard:

eap6_need_triage

Fixed In Version:

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2012-06-05 03:04:02 UTC

Type:

Bug

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

---

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Embargoed:

Attachments:

Description	Flags
pom.xml	none

Description Rostislav Svoboda 2012-05-17 07:29:59 UTC

project_key: JBPAPP6

I must run WS performance tests only with unsigned jars, that's workaround suggested in JBPAPP-7713.

Maven repo zip doesn't contain all dependencies for jbossws-cxf-client.

{code}
[ERROR] Failed to execute goal on project jbossws-perf-tests: Could not resolve dependencies for project
org.jboss.ws.perf:jbossws-perf-tests:jar:2.0.0-SNAPSHOT: The following artifacts could not be resolved: 
org.apache.aries.blueprint:org.apache.aries.blueprint.core:jar:0.3-redhat-1, org.codehaus.jra:jra:jar:1.0-alpha-4-redhat-1,
org.apache.ant:ant:jar:1.8.3-redhat-1, commons-logging:commons-logging:jar:1.1.1-redhat-1, org.opensaml:opensaml:jar:
2.4.1-redhat-1, org.opensaml:xmltooling:jar:1.3.2-redhat-1, org.apache.cxf:cxf-rt-javascript:jar:2.4.6-redhat-1, 
com.sun.xml.fastinfoset:FastInfoset:jar:1.2.7-redhat-1: Could not find artifact org.apache.aries.blueprint:
org.apache.aries.blueprint.core:jar:0.3-redhat-1 
{code}


{code}
<dependency>
    <groupId>org.jboss.ws.cxf</groupId>
    <artifactId>jbossws-cxf-client</artifactId>
    <version>4.0.4.GA-redhat-1</version>
</dependency>
{code}

https://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-Performance/job/eap-60-ws-perf-stress/SF_PERF_TEST=basic.BasicTest,jdk=java16_default,label=perf22-eap/23/console

I must have unsigned jars, without that WS perf results won't hit performance release criteria. 

MEAD repo contains necessary files, but they are signed. Everything is maven based, manual unsigning is not possible.

Comment 1 Paul Gier 2012-05-17 13:21:16 UTC

Why is manual unsigning not possible?

Comment 2 Rostislav Svoboda 2012-05-17 14:50:38 UTC

Tests are maven based and I can't unsign MEAD repo by myself.

Comment 3 Rajesh Rajasekaran 2012-05-17 14:56:40 UTC

Rosta, are these test dependencies? If so can you use another repository for your test? 
If they are product dependencies that we are not packaging in the maven zip, then I see it as a bug.

Comment 4 Rostislav Svoboda 2012-05-17 15:02:39 UTC

IMPORTANT: this jira is not only about that I have or don't have access to unsigned jar.

More important is fact that customers can't use productized jbossws-cxf-client artifact because some artifacts are missing in maven repo zip aka build-your-app-repo.

That's the biggest problem because customers wouldn't be able to run productized WS client in their apps !!!

Comment 5 Paul Gier 2012-05-17 17:11:54 UTC

-If we add jbossws-cxf-client to the maven repo zip does that solve the issue?-
Just answering my own question, if this jar is required by customer we should add it to the Maven repo zip.

Comment 6 Shelly McGowan 2012-05-17 19:33:59 UTC

What's wrong with using the one from the EAP distribution:
/work/EAP-6.0.0.GA/jboss-eap-6.0/modules/org/jboss/ws/jaxws-client/main/jbossws-cxf-client-4.0.4.GA-redhat-1.jar

Comment 7 Paul Gier 2012-05-17 19:45:50 UTC

Sorry, I see that the jbossws-client jar is already in the maven repo zip and eap zip.  If these dependencies are not needed for running the testsuite, then they can be excluded in the testsuite poms.  If they are needed, then a separate qa repository could be created which has the needed artifacts.  

For customers, they could use the as bom which will excluded these extra dependencies.  But we should also make these dependencies optional in the poms so that they are not automatically included.

Comment 8 Rostislav Svoboda 2012-05-18 07:50:48 UTC

jbossws-cxf-client is umbrella for all WS client dependencies, you must include all jbossws-cxf-client dependencies into maven repo zip. Please talk to Alessio too.

I don't use maven repo zip for testsuite but for performance test. The only "productized" dependency I include is:
{code}
<dependency>
    <groupId>org.jboss.ws.cxf</groupId>
    <artifactId>jbossws-cxf-client</artifactId>
    <version>4.0.4.GA-redhat-1</version>
</dependency>
{code}

Customers will use only jbossws-cxf-client dependency, I don't expect that they will manually specify only available dependencies in maven repo zip.

Comment 9 Alessio Soldano 2012-05-18 08:36:04 UTC

Please keep in mind that Rotislav's dependency on org.jboss.ws.cxf:jbossws-cxf-client artifact only is the way people is expected to set a dependency on the jbossws-cxf client. So this MUST work without having to manually exclude anything.

Comment 10 Carlo de Wolf 2012-05-18 12:34:45 UTC

Attachment: Added: pom.xml

Comment 11 Carlo de Wolf 2012-05-18 12:35:40 UTC

The attached pom works for me to resolve the dependency.

I can't judge whether I have enough runtime dependencies to actually execute a test though.

Comment 12 Alessio Soldano 2012-05-18 12:54:33 UTC

Carlo, it really depends on what you have in your local filesystem copy of the repo.
Here the problem is that CXF cxf-rt-soap-binding module has a dependency on Aries. That dependency needs to be at "provided" scope and that's set in the CXF maven parent, into a dependency-management block that of course apply to any cxf module importing that parent.
The productization guys are likely stripping that block away. As a consequence, the dependency moves from provided to compile scope, which then reveal this missing dependency issue. While we might probably build Aries and anything else and add to the repo, the problem here is that the productized artifacts are having the dependency trees changed. Which is potentially a critical issue.

Comment 13 Paul Gier 2012-05-18 15:09:11 UTC

Carlo's example is basically the usage we were/are designing for.  The jboss-as-parent contains the exclusion configuration to prevent unnecessary dependencies being brought into the build.  That should at least provide a workaround for QA to continue testing.

However, Alessio is correct that we shouldn't modify the dependency scopes during productization, so we will try to restore the original scope configuration, and then deal with any remaining missing dependencies individually.

Comment 14 Paul Gier 2012-05-20 20:31:21 UTC

I made some changes to the eap boms to exclude the apache blueprint, codehaus jra, ant, and opensaml dependencies, and updated the maven repo zip to include commons-logging and fastinfoset.

There is a new test in the Maven repo build which resolves jbossws-cxf-client against the maven repo zip.
http://git.app.eng.bos.redhat.com/?p=jboss-eap/maven-repository-testsuite.git;a=commitdiff;h=e234ee850f4034b4ff6c86524d3d09d7be6f4774

Rosta, can you try building again using a recent build of the Maven repo zip?
https://hudson.qa.jboss.com/hudson/job/JBoss-EAP-6.0.x-Maven-Repository/

Comment 15 Rostislav Svoboda 2012-05-21 05:34:25 UTC

>> Rosta, can you try building again using a recent build of the Maven repo zip?


I'll try it but currently there is more important issue I must work on - JBossWS testsuite execution.

>> JBossWS performance

During weekend I tried to setup dependencies for official ER8 build, firs perf job is in queue but perf lab is occupied by soak tests.

With upstream client it's enough to setup dependency on jbossws-cxf-client. But with ER8 build I must use more dependencies (cxf-rt-ws-security, wss4j)
{code}
            <dependencyManagement>
                <dependencies>
                    <dependency>
                        <groupId>org.jboss.as</groupId>
                        <artifactId>jboss-as-parent</artifactId>
                        <version>7.1.2.Final-redhat-1</version>
                        <type>pom</type>
                        <scope>import</scope>
                    </dependency>
                </dependencies>
            </dependencyManagement>
            <dependencies>
                <dependency>
                    <groupId>org.jboss.ws.cxf</groupId>
                    <artifactId>jbossws-cxf-client</artifactId>
                    <scope>test</scope>
                </dependency>
                <dependency>
                    <groupId>commons-lang</groupId>
                    <artifactId>commons-lang</artifactId>
                    <scope>test</scope>
                </dependency>
                <dependency>
                    <groupId>org.apache.ws.security</groupId>
                    <artifactId>wss4j</artifactId>
                    <scope>test</scope>
                </dependency>
                <dependency>
                    <groupId>org.apache.cxf</groupId>
                    <artifactId>cxf-rt-ws-security</artifactId>
                    <scope>test</scope>
                </dependency>

            </dependencies>
{code}

Comment 16 Rostislav Svoboda 2012-05-21 06:08:37 UTC

With ER7 I executed WS perf tests only with jbossws-cxf-client dependency.

{code}
        <profile>
            <id>eap600-cxf</id>  
            <properties>
                <include.serviceName>true</include.serviceName>
            </properties>
            <dependencies>
                <dependency>
                    <groupId>org.jboss.ws.cxf</groupId>
                    <artifactId>jbossws-cxf-client</artifactId>
                    <version>4.0.4.GA-redhat-1</version>
                    <scope>test</scope>
                </dependency>
            </dependencies>
        </profile>
{code}

Comment 17 Alessio Soldano 2012-05-21 09:32:50 UTC

*WHY* are org.apache.cxf:cxf-rt-ws-security and org.apache.ws.security:wss4j dependencies removed in the productization process?!?!

Comment 18 Rostislav Svoboda 2012-05-21 10:46:17 UTC

More work will be necessary on this topic.

My tests started few minutes ago but ended quite quickly:

{code}
[runTest(bash)] OUT > Tests in error: 
[runTest(bash)] OUT >   testCustom(org.jboss.test.ws.jaxws.benchmark.CustomPerfJUnitTest): 
javax.xml.ws.spi.Provider: Provider org.jboss.wsf.stack.cxf.client.ProviderImpl could not be instantiated:
java.lang.NoClassDefFoundError: org/apache/cxf/jaxws22/spi/ProviderImpl
{code}

Using BOM for dependencies seem to be more problematic than I expected :)

Comment 19 Rostislav Svoboda 2012-05-21 11:51:55 UTC

jbossws-cxf-client:4.0.4.GA-redhat-1 has less dependencies (used with org.jboss.as:jboss-as-parent:7.1.2.Final-redhat-1 BOM) when comparing to dependency-tree.txt attached to JBPAPP-9069. See 'Building JBoss Web Services - Stack CXF Testsuite 4.0.4.GA' section for example.

Dependency tree for configuration mentioned in my [first comment today|https://issues.jboss.org/browse/JBPAPP-9042?focusedCommentId=12694198&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12694198]:

{code}
[INFO] --- maven-dependency-plugin:2.1:tree (default-cli) @ jbossws-perf-tests ---
[INFO] org.jboss.ws.perf:jbossws-perf-tests:jar:2.0.0-SNAPSHOT
[INFO] +- junit:junit:jar:3.8.1:test
[INFO] +- javax.ejb:ejb-api:jar:3.0:test
[INFO] +- net.sf.m-m-m:mmm-util-core:jar:1.1.1:test
[INFO] |  \- org.slf4j:slf4j-api:jar:1.6.1-redhat-1:test (version managed from 1.5.6)
[INFO] +- jfree:jfreechart:jar:1.0.12:test
[INFO] |  \- jfree:jcommon:jar:1.0.15:test
[INFO] +- net.sf.opencsv:opencsv:jar:2.1:test
[INFO] +- org.jboss.ws.cxf:jbossws-cxf-client:jar:4.0.4.GA-redhat-1:test
[INFO] |  +- org.jboss.ws:jbossws-api:jar:1.0.0.GA-redhat-1:test
[INFO] |  +- org.jboss.ws:jbossws-common:jar:2.0.4.GA-redhat-1:test
[INFO] |  +- org.jboss.ws:jbossws-common-tools:jar:1.0.1.GA-redhat-1:test
[INFO] |  +- org.jboss.ws:jbossws-spi:jar:2.0.3.GA-redhat-1:test
[INFO] |  +- org.jboss.ws.cxf:jbossws-cxf-factories:jar:4.0.4.GA-redhat-1:test
[INFO] |  +- org.jboss.ws.cxf:jbossws-cxf-transports-httpserver:jar:4.0.4.GA-redhat-1:test
[INFO] |  |  +- org.jboss.ws.projects:jaxws-jboss-httpserver-httpspi:jar:1.0.1.GA-redhat-1:test
[INFO] |  |  \- org.jboss.com.sun.httpserver:httpserver:jar:1.0.1.Final-redhat-1:test
[INFO] |  +- org.apache.cxf:cxf-rt-frontend-simple:jar:2.4.6-redhat-1:test
[INFO] |  |  +- org.osgi:org.osgi.core:jar:4.2.0-redhat-1:test
[INFO] |  |  \- org.apache.cxf:cxf-rt-core:jar:2.4.6-redhat-1:test
[INFO] |  |     \- javax.mail:mail:jar:1.4.4-redhat-1:test
[INFO] |  +- org.apache.cxf:cxf-rt-databinding-jaxb:jar:2.4.6-redhat-1:test
[INFO] |  |  +- com.sun.xml.bind:jaxb-impl:jar:2.2.5-redhat-1:test
[INFO] |  |  |  +- com.sun.istack:istack-commons-runtime:jar:2.6.1-redhat-1:test
[INFO] |  |  |  |  \- javax.activation:activation:jar:1.1.1-redhat-1:test
[INFO] |  |  |  \- com.sun.xml.txw2:txw2:jar:20110809-redhat-1:test
[INFO] |  |  \- com.sun.xml.bind:jaxb-xjc:jar:2.2.5-redhat-1:test
[INFO] |  |     +- com.sun.codemodel:codemodel:jar:2.6-redhat-1:test
[INFO] |  |     +- com.sun.istack:istack-commons-tools:jar:2.6.1-redhat-1:test
[INFO] |  |     |  \- com.sun:tools:jar:1.5:system
[INFO] |  |     +- com.github.relaxng:relaxngDatatype:jar:2011.1-redhat-1:test
[INFO] |  |     +- com.sun.xsom:xsom:jar:20110809-redhat-1:test
[INFO] |  |     \- xml-resolver:xml-resolver:jar:1.2-redhat-1:test
[INFO] |  +- org.apache.cxf:cxf-tools-common:jar:2.4.6-redhat-1:test
[INFO] |  +- org.apache.velocity:velocity:jar:1.6.3-redhat-1:test
[INFO] |  +- org.codehaus.woodstox:stax2-api:jar:3.1.1-redhat-1:test
[INFO] |  +- org.codehaus.woodstox:woodstox-core-lgpl:jar:4.1.1-redhat-1:test
[INFO] |  +- org.jboss.spec.javax.xml.rpc:jboss-jaxrpc-api_1.1_spec:jar:1.0.1.Final-redhat-1:test
[INFO] |  |  \- org.jboss.spec.javax.servlet:jboss-servlet-api_3.0_spec:jar:1.0.1.Final-redhat-1:test
[INFO] |  +- javax.jws:jsr181-api:jar:1.0-MR1-redhat-1:test
[INFO] |  +- org.jboss.spec.javax.xml.bind:jboss-jaxb-api_2.2_spec:jar:1.0.4.Final-redhat-1:test
[INFO] |  +- org.jboss.spec.javax.xml.ws:jboss-jaxws-api_2.2_spec:jar:2.0.1.Final-redhat-1:test
[INFO] |  +- org.jboss.spec.javax.xml.soap:jboss-saaj-api_1.3_spec:jar:1.0.2.Final-redhat-1:test
[INFO] |  +- org.jboss:jboss-common-core:jar:2.2.17.GA-redhat-1:test
[INFO] |  +- log4j:log4j:jar:1.2.16-redhat-1:test
[INFO] |  +- org.jboss.logging:jboss-logging:jar:3.1.1.GA-redhat-1:test
[INFO] |  \- org.apache.neethi:neethi:jar:3.0.1-redhat-1:test
[INFO] |     \- org.codehaus.woodstox:woodstox-core-asl:jar:4.1.1-redhat-1:test
[INFO] +- commons-lang:commons-lang:jar:2.6-redhat-1:test
[INFO] +- org.apache.ws.security:wss4j:jar:1.6.5-redhat-1:test
[INFO] |  \- org.apache.santuario:xmlsec:jar:1.5.1-redhat-1:test
[INFO] \- org.apache.cxf:cxf-rt-ws-security:jar:2.4.6-redhat-1:test
[INFO]    +- org.apache.cxf:cxf-api:jar:2.4.6-redhat-1:test
[INFO]    |  \- wsdl4j:wsdl4j:jar:1.6.2-redhat-1:test
[INFO]    +- org.apache.cxf:cxf-common-utilities:jar:2.4.6-redhat-1:test
[INFO]    \- xalan:xalan:jar:2.7.1-redhat-1:test
[INFO]       \- xalan:serializer:jar:2.7.1-redhat-1:test
{code}

Comment 20 Alessio Soldano 2012-05-21 12:07:16 UTC

The org.apache.cxf:cxf-rt-frontend-jaxws:jar is missing. Again *WHY* is that (also) removed from the dependency tree?!?!

Comment 21 Carlo de Wolf 2012-05-21 12:10:36 UTC

For reference the product patches are at http://pkgs.devel.redhat.com/cgit/rpms/jbossws-cxf/tree/?h=jb-eap-6-rhel-6

Comment 22 Rostislav Svoboda 2012-05-21 12:25:33 UTC

I tried [Hudson build #584 for maven repo zip|https://hudson.qa.jboss.com/hudson/job/JBoss-EAP-6.0.x-Maven-Repository/584/].

pom.xml configuration
{code}
        <profile>
            <id>eap600-cxf-pure</id>
            <properties>
                <include.serviceName>true</include.serviceName>
            </properties>
            <dependencies>
                <dependency>
                    <groupId>org.jboss.ws.cxf</groupId>
                    <artifactId>jbossws-cxf-client</artifactId>
                    <version>4.0.4.GA-redhat-1</version>
                    <scope>test</scope>
                </dependency>
            </dependencies>
        </profile>
{code}

MVN configured to use default mvn repository (http://repo1.maven.org/maven2/) + local repo based on downloaded zip (<url>file:///home/rsvoboda/TESTING/jboss-eap-6.0.0.CR-maven-repository</url>)

I was able to compile tests and run set of perf tests locally. 
New maven repo zip from run #584 can be used for client side dependencies with just jbossws-cxf-client dependency. BOM wasn't used at all.

Comment 23 Rostislav Svoboda 2012-05-21 13:05:12 UTC

Using BOM file causes missing dependencies problems
 - without BOM definition there are 92 dependencies for jbossws-cxf-client
 - with BOM definition there are only 43 dependencies for jbossws-cxf-client

Tested with maven repo zip from hudson #584.

----
{code}
<profile>
            <id>eap600-cxf-pure</id>
            <properties>
                <include.serviceName>true</include.serviceName>
            </properties>
            <dependencies>
                <dependency>
                    <groupId>org.jboss.ws.cxf</groupId>
                    <artifactId>jbossws-cxf-client</artifactId>
                    <version>4.0.4.GA-redhat-1</version>
                    <scope>test</scope>
                </dependency>
            </dependencies>
        </profile>
{code}
dependency tree:
{code}
[INFO] Scanning for projects...
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building JBoss Web Services - Performance 2.0.0-SNAPSHOT 2.0.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-dependency-plugin:2.1:tree (default-cli) @ jbossws-perf-tests ---
[INFO] org.jboss.ws.perf:jbossws-perf-tests:jar:2.0.0-SNAPSHOT
[INFO] +- junit:junit:jar:3.8.1:test
[INFO] +- javax.ejb:ejb-api:jar:3.0:test
[INFO] +- net.sf.m-m-m:mmm-util-core:jar:1.1.1:test
[INFO] |  \- org.slf4j:slf4j-api:jar:1.5.6:test
[INFO] +- jfree:jfreechart:jar:1.0.12:test
[INFO] |  \- jfree:jcommon:jar:1.0.15:test
[INFO] +- net.sf.opencsv:opencsv:jar:2.1:test
[INFO] \- org.jboss.ws.cxf:jbossws-cxf-client:jar:4.0.4.GA-redhat-1:test
[INFO]    +- org.jboss.ws:jbossws-api:jar:1.0.0.GA-redhat-1:test
[INFO]    +- org.jboss.ws:jbossws-common:jar:2.0.4.GA-redhat-1:test
[INFO]    +- org.jboss.ws:jbossws-common-tools:jar:1.0.1.GA-redhat-1:test
[INFO]    |  \- gnu-getopt:getopt:jar:1.0.13-redhat-1:test
[INFO]    +- org.jboss.ws:jbossws-spi:jar:2.0.3.GA-redhat-1:test
[INFO]    +- org.jboss.ws.cxf:jbossws-cxf-factories:jar:4.0.4.GA-redhat-1:test
[INFO]    +- org.jboss.ws.cxf:jbossws-cxf-transports-httpserver:jar:4.0.4.GA-redhat-1:test
[INFO]    |  +- org.jboss.ws.projects:jaxws-jboss-httpserver-httpspi:jar:1.0.1.GA-redhat-1:test
[INFO]    |  +- org.apache.cxf:cxf-common-utilities:jar:2.4.6-redhat-1:test
[INFO]    |  |  \- org.apache.ws.xmlschema:xmlschema-core:jar:2.0.2-redhat-1:test
[INFO]    |  \- org.jboss.com.sun.httpserver:httpserver:jar:1.0.1.Final-redhat-1:test
[INFO]    +- org.apache.cxf:cxf-rt-bindings-soap:jar:2.4.6-redhat-1:test
[INFO]    |  +- org.osgi:org.osgi.core:jar:4.2.0-redhat-1:test
[INFO]    |  \- org.apache.cxf:cxf-api:jar:2.4.6-redhat-1:test
[INFO]    +- org.apache.cxf:cxf-rt-bindings-http:jar:2.4.6-redhat-1:test
[INFO]    |  \- org.apache.cxf:cxf-rt-bindings-xml:jar:2.4.6-redhat-1:test
[INFO]    +- org.apache.cxf:cxf-rt-bindings-object:jar:2.4.6-redhat-1:test
[INFO]    +- org.apache.cxf:cxf-rt-bindings-coloc:jar:2.4.6-redhat-1:test
[INFO]    |  \- org.apache.cxf:cxf-rt-core:jar:2.4.6-redhat-1:test
[INFO]    |     \- javax.mail:mail:jar:1.4.4-redhat-1:test
[INFO]    +- org.apache.cxf:cxf-rt-frontend-jaxws:jar:2.4.6-redhat-1:test
[INFO]    |  +- xml-resolver:xml-resolver:jar:1.2-redhat-1:test
[INFO]    |  \- org.apache.cxf:cxf-rt-ws-addr:jar:2.4.6-redhat-1:test
[INFO]    +- org.apache.cxf:cxf-rt-transports-http:jar:2.4.6-redhat-1:test
[INFO]    |  +- org.apache.cxf:cxf-rt-transports-common:jar:2.4.6-redhat-1:test
[INFO]    |  \- org.springframework:spring-web:jar:2.5.6.SEC03:test
[INFO]    |     +- org.springframework:spring-beans:jar:2.5.6.SEC03:test
[INFO]    |     \- org.springframework:spring-core:jar:2.5.6.SEC03:test
[INFO]    +- org.apache.cxf:cxf-rt-transports-jms:jar:2.4.6-redhat-1:test
[INFO]    |  +- org.apache.cxf:cxf-rt-management:jar:2.4.6-redhat-1:test
[INFO]    |  +- org.jboss.spec.javax.jms:jboss-jms-api_1.1_spec:jar:1.0.1.Final-redhat-1:test
[INFO]    |  +- org.springframework:spring-jms:jar:2.5.6.SEC03:test
[INFO]    |  |  +- commons-pool:commons-pool:jar:1.3:test
[INFO]    |  |  \- org.springframework:spring-context-support:jar:2.5.6.SEC03:test
[INFO]    |  +- org.springframework:spring-context:jar:2.5.6.SEC03:test
[INFO]    |  |  \- aopalliance:aopalliance:jar:1.0:test
[INFO]    |  +- org.springframework:spring-tx:jar:2.5.6.SEC03:test
[INFO]    |  +- com.sun.xml.bind:jaxb-impl:jar:2.2.5-redhat-1:test
[INFO]    |  |  +- com.sun.istack:istack-commons-runtime:jar:2.6.1-redhat-1:test
[INFO]    |  |  |  +- stax:stax-api:jar:1.0.1:test
[INFO]    |  |  |  \- javax.activation:activation:jar:1.1.1-redhat-1:test
[INFO]    |  |  \- com.sun.xml.txw2:txw2:jar:20110809-redhat-1:test
[INFO]    |  \- com.sun.xml.bind:jaxb-xjc:jar:2.2.5-redhat-1:test
[INFO]    |     +- com.sun.codemodel:codemodel:jar:2.6-redhat-1:test
[INFO]    |     +- com.sun.xml.dtd-parser:dtd-parser:jar:1.2-redhat-1:test
[INFO]    |     +- com.sun.istack:istack-commons-tools:jar:2.6.1-redhat-1:test
[INFO]    |     |  \- com.sun:tools:jar:1.5:system
[INFO]    |     +- com.github.relaxng:relaxngDatatype:jar:2011.1-redhat-1:test
[INFO]    |     +- org.kohsuke.rngom:rngom:jar:201103-redhat-1:test
[INFO]    |     \- com.sun.xsom:xsom:jar:20110809-redhat-1:test
[INFO]    +- org.apache.cxf:cxf-rt-transports-local:jar:2.4.6-redhat-1:test
[INFO]    +- org.apache.cxf:cxf-rt-ws-rm:jar:2.4.6-redhat-1:test
[INFO]    +- org.apache.cxf:cxf-rt-ws-policy:jar:2.4.6-redhat-1:test
[INFO]    +- org.apache.cxf:cxf-rt-ws-security:jar:2.4.6-redhat-1:test
[INFO]    |  +- org.apache.ws.security:wss4j:jar:1.6.5-redhat-1:test
[INFO]    |  +- commons-logging:commons-logging:jar:1.1.1-redhat-1:test
[INFO]    |  \- xalan:xalan:jar:2.7.1-redhat-1:test
[INFO]    |     \- xalan:serializer:jar:2.7.1-redhat-1:test
[INFO]    +- org.apache.cxf:cxf-tools-java2ws:jar:2.4.6-redhat-1:test
[INFO]    |  +- wsdl4j:wsdl4j:jar:1.6.2-redhat-1:test
[INFO]    |  \- org.apache.cxf:cxf-rt-databinding-aegis:jar:2.4.6-redhat-1:test
[INFO]    +- org.apache.cxf:cxf-tools-wsdlto-core:jar:2.4.6-redhat-1:test
[INFO]    |  \- org.apache.cxf:cxf-tools-validator:jar:2.4.6-redhat-1:test
[INFO]    +- org.apache.cxf:cxf-tools-wsdlto-databinding-jaxb:jar:2.4.6-redhat-1:test
[INFO]    +- org.apache.cxf:cxf-tools-wsdlto-frontend-jaxws:jar:2.4.6-redhat-1:test
[INFO]    +- org.apache.cxf.xjcplugins:cxf-xjc-boolean:jar:2.4.0-redhat-1:test
[INFO]    +- org.apache.cxf.xjcplugins:cxf-xjc-dv:jar:2.4.0-redhat-1:test
[INFO]    +- org.apache.cxf.xjcplugins:cxf-xjc-ts:jar:2.4.0-redhat-1:test
[INFO]    +- org.apache.cxf:cxf-rt-frontend-simple:jar:2.4.6-redhat-1:test
[INFO]    +- org.apache.cxf:cxf-rt-databinding-jaxb:jar:2.4.6-redhat-1:test
[INFO]    +- org.apache.cxf:cxf-tools-common:jar:2.4.6-redhat-1:test
[INFO]    +- org.apache.velocity:velocity:jar:1.6.3-redhat-1:test
[INFO]    |  \- oro:oro:jar:2.0.8:test
[INFO]    +- commons-collections:commons-collections:jar:3.2.1-redhat-1:test
[INFO]    +- commons-lang:commons-lang:jar:2.6-redhat-1:test
[INFO]    +- org.codehaus.woodstox:stax2-api:jar:3.1.1-redhat-1:test
[INFO]    +- org.apache.santuario:xmlsec:jar:1.5.1-redhat-1:test
[INFO]    +- org.codehaus.woodstox:woodstox-core-lgpl:jar:4.1.1-redhat-1:test
[INFO]    +- com.sun.xml.fastinfoset:FastInfoset:jar:1.2.7-redhat-1:test
[INFO]    +- asm:asm:jar:3.3.1-redhat-1:test
[INFO]    +- org.jboss.spec.javax.xml.rpc:jboss-jaxrpc-api_1.1_spec:jar:1.0.1.Final-redhat-1:test
[INFO]    |  \- org.jboss.spec.javax.servlet:jboss-servlet-api_3.0_spec:jar:1.0.1.Final-redhat-1:test
[INFO]    +- javax.jws:jsr181-api:jar:1.0-MR1-redhat-1:test
[INFO]    +- org.jboss.spec.javax.xml.bind:jboss-jaxb-api_2.2_spec:jar:1.0.4.Final-redhat-1:test
[INFO]    +- org.jboss.spec.javax.xml.ws:jboss-jaxws-api_2.2_spec:jar:2.0.1.Final-redhat-1:test
[INFO]    +- org.jboss.spec.javax.xml.soap:jboss-saaj-api_1.3_spec:jar:1.0.2.Final-redhat-1:test
[INFO]    +- org.jboss:jboss-common-core:jar:2.2.17.GA-redhat-1:test
[INFO]    +- log4j:log4j:jar:1.2.16-redhat-1:test
[INFO]    +- org.jboss.logging:jboss-logging:jar:3.1.1.GA-redhat-1:test
[INFO]    \- org.apache.neethi:neethi:jar:3.0.1-redhat-1:test
[INFO]       \- org.codehaus.woodstox:woodstox-core-asl:jar:4.1.1-redhat-1:test
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 10.361s
[INFO] Finished at: Mon May 21 14:53:14 CEST 2012
[INFO] Final Memory: 31M/713M
[INFO] ------------------------------------------------------------------------
{code}

----
{code}
        <profile>
            <id>eap600-cxf-experiment</id>
            <properties>
                <include.serviceName>true</include.serviceName>
            </properties>
            <dependencyManagement>
                <dependencies>
                    <dependency>
                        <groupId>org.jboss.as</groupId>
                        <artifactId>jboss-as-parent</artifactId>
                        <version>7.1.2.Final-redhat-1</version>
                        <type>pom</type>
                        <scope>import</scope>
                    </dependency>
                </dependencies>
            </dependencyManagement>
            <dependencies>
                <dependency>
                    <groupId>org.jboss.ws.cxf</groupId>
                    <artifactId>jbossws-cxf-client</artifactId>
                    <version>4.0.4.GA-redhat-1</version>
                    <scope>test</scope>
                </dependency>
            </dependencies>
        </profile>
{code}
dependency tree:
{code}
[INFO] Scanning for projects...
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building JBoss Web Services - Performance 2.0.0-SNAPSHOT 2.0.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-dependency-plugin:2.1:tree (default-cli) @ jbossws-perf-tests ---
[INFO] org.jboss.ws.perf:jbossws-perf-tests:jar:2.0.0-SNAPSHOT
[INFO] +- junit:junit:jar:3.8.1:test
[INFO] +- javax.ejb:ejb-api:jar:3.0:test
[INFO] +- net.sf.m-m-m:mmm-util-core:jar:1.1.1:test
[INFO] |  \- org.slf4j:slf4j-api:jar:1.6.1-redhat-1:test (version managed from 1.5.6)
[INFO] +- jfree:jfreechart:jar:1.0.12:test
[INFO] |  \- jfree:jcommon:jar:1.0.15:test
[INFO] +- net.sf.opencsv:opencsv:jar:2.1:test
[INFO] \- org.jboss.ws.cxf:jbossws-cxf-client:jar:4.0.4.GA-redhat-1:test
[INFO]    +- org.jboss.ws:jbossws-api:jar:1.0.0.GA-redhat-1:test
[INFO]    +- org.jboss.ws:jbossws-common:jar:2.0.4.GA-redhat-1:test
[INFO]    +- org.jboss.ws:jbossws-common-tools:jar:1.0.1.GA-redhat-1:test
[INFO]    +- org.jboss.ws:jbossws-spi:jar:2.0.3.GA-redhat-1:test
[INFO]    +- org.jboss.ws.cxf:jbossws-cxf-factories:jar:4.0.4.GA-redhat-1:test
[INFO]    +- org.jboss.ws.cxf:jbossws-cxf-transports-httpserver:jar:4.0.4.GA-redhat-1:test
[INFO]    |  +- org.jboss.ws.projects:jaxws-jboss-httpserver-httpspi:jar:1.0.1.GA-redhat-1:test
[INFO]    |  +- org.apache.cxf:cxf-common-utilities:jar:2.4.6-redhat-1:test
[INFO]    |  \- org.jboss.com.sun.httpserver:httpserver:jar:1.0.1.Final-redhat-1:test
[INFO]    +- org.apache.cxf:cxf-rt-frontend-simple:jar:2.4.6-redhat-1:test
[INFO]    |  +- org.osgi:org.osgi.core:jar:4.2.0-redhat-1:test
[INFO]    |  +- org.apache.cxf:cxf-api:jar:2.4.6-redhat-1:test
[INFO]    |  |  \- wsdl4j:wsdl4j:jar:1.6.2-redhat-1:test
[INFO]    |  \- org.apache.cxf:cxf-rt-core:jar:2.4.6-redhat-1:test
[INFO]    |     \- javax.mail:mail:jar:1.4.4-redhat-1:test
[INFO]    +- org.apache.cxf:cxf-rt-databinding-jaxb:jar:2.4.6-redhat-1:test
[INFO]    |  +- com.sun.xml.bind:jaxb-impl:jar:2.2.5-redhat-1:test
[INFO]    |  |  +- com.sun.istack:istack-commons-runtime:jar:2.6.1-redhat-1:test
[INFO]    |  |  |  \- javax.activation:activation:jar:1.1.1-redhat-1:test
[INFO]    |  |  \- com.sun.xml.txw2:txw2:jar:20110809-redhat-1:test
[INFO]    |  \- com.sun.xml.bind:jaxb-xjc:jar:2.2.5-redhat-1:test
[INFO]    |     +- com.sun.codemodel:codemodel:jar:2.6-redhat-1:test
[INFO]    |     +- com.sun.istack:istack-commons-tools:jar:2.6.1-redhat-1:test
[INFO]    |     |  \- com.sun:tools:jar:1.5:system
[INFO]    |     +- com.github.relaxng:relaxngDatatype:jar:2011.1-redhat-1:test
[INFO]    |     +- com.sun.xsom:xsom:jar:20110809-redhat-1:test
[INFO]    |     \- xml-resolver:xml-resolver:jar:1.2-redhat-1:test
[INFO]    +- org.apache.cxf:cxf-tools-common:jar:2.4.6-redhat-1:test
[INFO]    +- org.apache.velocity:velocity:jar:1.6.3-redhat-1:test
[INFO]    +- org.codehaus.woodstox:stax2-api:jar:3.1.1-redhat-1:test
[INFO]    +- org.codehaus.woodstox:woodstox-core-lgpl:jar:4.1.1-redhat-1:test
[INFO]    +- org.jboss.spec.javax.xml.rpc:jboss-jaxrpc-api_1.1_spec:jar:1.0.1.Final-redhat-1:test
[INFO]    |  \- org.jboss.spec.javax.servlet:jboss-servlet-api_3.0_spec:jar:1.0.1.Final-redhat-1:test
[INFO]    +- javax.jws:jsr181-api:jar:1.0-MR1-redhat-1:test
[INFO]    +- org.jboss.spec.javax.xml.bind:jboss-jaxb-api_2.2_spec:jar:1.0.4.Final-redhat-1:test
[INFO]    +- org.jboss.spec.javax.xml.ws:jboss-jaxws-api_2.2_spec:jar:2.0.1.Final-redhat-1:test
[INFO]    +- org.jboss.spec.javax.xml.soap:jboss-saaj-api_1.3_spec:jar:1.0.2.Final-redhat-1:test
[INFO]    +- org.jboss:jboss-common-core:jar:2.2.17.GA-redhat-1:test
[INFO]    +- log4j:log4j:jar:1.2.16-redhat-1:test
[INFO]    +- org.jboss.logging:jboss-logging:jar:3.1.1.GA-redhat-1:test
[INFO]    \- org.apache.neethi:neethi:jar:3.0.1-redhat-1:test
[INFO]       \- org.codehaus.woodstox:woodstox-core-asl:jar:4.1.1-redhat-1:test
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 7.339s
[INFO] Finished at: Mon May 21 14:53:36 CEST 2012
[INFO] Final Memory: 23M/733M
[INFO] ------------------------------------------------------------------------
{code}

----

Comment 24 Rajesh Rajasekaran 2012-05-21 13:23:01 UTC

Labels: Added: eap6_need_triage

Comment 25 Paul Gier 2012-05-21 13:49:54 UTC

{quote}WHY are org.apache.cxf:cxf-rt-ws-security and org.apache.ws.security:wss4j dependencies removed in the productization process?!?!{quote}
These are not removed by productization.  If you look at the usage of the cxf-client dependency in the testsuite setup above, dependencyManagement information is coming from jboss-as-parent.  The jboss-as-parent pom (same as upstream) specifies that cxf-rs-ws-security (and transitively wss4j) should be excluded from the dependency tree of jbossws-cxf-client.  Same issue with cxf-rt-frontend-jaxws.

{quote}With ER7 I executed WS perf tests only with jbossws-cxf-client dependency.{quote}
Rosta, did you try this the nightly build of the Maven repo zip?

Comment 26 Alessio Soldano 2012-05-21 14:01:42 UTC

Paul, I can accept you're not going to consider org.jboss.ws.jbossws-cxf-client as the entry point for setting client side ws dependencies (which still is one of the reason it was created for), but then please explain what a customer is supposed to set in his client side ws maven project to have proper dependencies.

Comment 29 Paul Gier 2012-05-21 14:29:47 UTC

See the maven repository testsuite commit I linked above.  Customer sets only the jbossws-cxf-client dependency, just like what is done upstream.  Doing this the dependency tree should be the same.
{code:xml}
<dependencies>
  <dependency>
    <groupId>org.jboss.ws.cxf</groupId>
    <artifactId>jbossws-cxf-client</artifactId>
    <version>@version.org.jboss.ws.cxf@</version>
    <type>pom</type>
  </dependency>
</dependencies>
{code}

The difference occurs if the user (QA in this case) adds dependencyManagement which imports the jboss-as-parent pom which contains a section like this (same as upstream).
{code:xml}
<dependency>
    <groupId>org.jboss.ws.cxf</groupId>
    <artifactId>jbossws-cxf-client</artifactId>
    <version>${version.org.jboss.ws.cxf}</version>
    <exclusions>
        <exclusion>
            <groupId>asm</groupId>
            <artifactId>asm</artifactId>
        </exclusion>
        ...
        <exclusion>
            <groupId>org.apache.cxf</groupId>
            <artifactId>cxf-rt-ws-security</artifactId>
        </exclusion>
        ...
    </exclusions>
</dependency>
{code}

This causes maven to apply the exclusion rules to your current build.  So a dependency on jbossws-cxf-client without dependency management gets the full dep tree.  A dependency on jbossws-cxf-client with dependency management imported causes the reduced dependency tree.

Comment 30 Rostislav Svoboda 2012-05-21 14:38:27 UTC

I used dependencyManagement because it was mentioned in attached pom file.

I wanted to use just jbossws-cxf-client dependency but I was blocked by unavailable dependencies.

Comment 31 Alessio Soldano 2012-05-21 14:52:37 UTC

OK, on the more general topic of quickly setting a dependency on client ws artifacts, we can sum this up as follows:
* the org.jboss.ws:jbossws-cxf-client should still be usable and enough also with productized version
* the user (QA in this case) will need to avoid setting the jboss-as-parent as parent to the project, as that comes with a dependencyManagement block that is probably too strict and exclusions and basically removes artifacts that are meant to come through jbossws-cxf-client as transitive dependencies.

Comment 32 Rostislav Svoboda 2012-06-04 11:04:42 UTC

Verified on EAP 6.0.0 CR1

Comment 33 Tom WELLS 2012-06-05 03:04:02 UTC

Release Notes Docs Status: Added: Not Required

Comment 34 Carlo de Wolf 2012-06-22 07:09:50 UTC

Link: Added: This issue is related to JBPAPP-9362

Comment 35 Anne-Louise Tangring 2012-11-05 17:55:45 UTC

Release Notes Docs Status: Removed: Not Required 
Docs QE Status: Removed: NEW