[
https://issues.jboss.org/browse/WFLY-3369?page=com.atlassian.jira.plugin....
]
Zhang Boya commented on WFLY-3369:
----------------------------------
To Jim Ma:
It's really simple to reproduce this issue, for example, based on contract-first
principle, to generate JAX-WS client classes from WSDL. Then try to invoke the JAX-WS by
using these classes, by default the JDK would give a default implementation, such as
'JAX-WS RI 2.2.4-b01: Stub', it works well either on JDK 1.7.0_25 or JDK 1.7.0_55.
But the response time increased since to add jboss-ws-jaxws-client and jbossws-cxf-client
related JAR files.
To Tomaz:
This issue can be reproduced even though the JBoss AS/WildFly doesn't startup. Just
add the JAR files to the classpath is enough. I have upgraded the JAR files by using
latest JBossWS - CXF 4.3.x. This issue still exist.
Performance issue of jaxws-client on JDK 1.7.0_55
-------------------------------------------------
Key: WFLY-3369
URL:
https://issues.jboss.org/browse/WFLY-3369
Project: WildFly
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: JBoss AS7 7.1.1.Final
Environment: Red Hat Enterprise 6.4, Solaris 10, JBoss AS 7.1.3
Reporter: Zhang Boya
Assignee: Alessio Soldano
Assume that a JAX-WS deploys on somewhere else, developer generates the JAX-WS client
side classes by using wsdl2java tools. These classes have been exported as
'exmaple-ws-client.jar'. When developer needs to access this JAX-WS in their web
application, this JAR file would be published with WAR file together. By default, the
JBoss AS would supply an instance of CXF's implementation for the JAX-WS client when
web application be deployed to JBoss AS. The class name of this JAX-WS client would be
'org.apache.cxf.jaxws.JaxWsClientProxy'. The JAX-WS invocations of client side got
a very bad performance since I upgraded JDK from 1.7.0_25 to 1.7.0_55, especially on
Solaris.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)