JBossWS testsuite reorganization
by Alessio Soldano
Folks,
with current development on jbossws trunk aimed at version 5, I believe
it's time consider rethinking the testsuite a bit.
Current status
--------------------
Historically, we've been running the integration tests against a JBoss
AS container that has to be started before the testsuite. The target
container is a vanilla distribution that suits with most of the tests,
except for few ones requiring a https connector or a specific security
domain to be available. Implementations of the
org.jboss.wsf.spi.deployer.Deployer interface are available for each
target container and allow deploying test archives as well as setting
security domains / https connector by internally relying on the
container management API.
Different maven profiles trigger different implementations of Deployer
(due to different artifact dependencies / classpath), allowing running
the testsuite the same way against different target containers. When it
comes to continuous integration, the idea is that a QA job first updates
a target container with the current jbossws libraries, then it starts
the container and runs the jbossws testsuite against it.
Issues / reasons for changing
---------------------------------------
The current approach is working pretty much fine, but suffers from some
limitations:
* it needs a container to be already running when the integration test
is triggered; it would be great if we could have the container started /
stopped by the test itself
* we're limited to running the testsuite against a predefined container
profile (standalone.xml, standalone-full.xml ): while most of the tests
makes sense when run against standalone.xml profile (because the
webservices subsystem is on in it), we have some tests requiring
subsystems available on different profiles (for instance, the messaging
subsystem which is in standalone-full.xml or the xts subsystem which is
in standalone-xts.xml). Currently we run the testsuite in Spring mode
against standalone-full.xml, basically because till CXF 2.7.x the
SOAP-over-JMS implementation has been available with Spring only. That's
not the case anymore, on CXF 3.0.0, so we'd likely have to test it in
both spring and non-spring mode, but that needs the messaging subsystem
which is not in standalone.xml
* we have few tests (but might have more in future) that actually
require further additional changes to the server; that includes adding
users, messaging queues, setting server side system properties at boot,
... The only way to achieve that atm is to have the QA job run a CLI
script to modify the server or set a system property on command line
when starting the server jvm
* we have tests affecting the server management model, for instance
changing the way the webservices subsystem model rewrites wsdl
soap:address attributes; that makes it impossible to run those tests at
the same time of any other tests
Proposals / idea
---------------------
I'm listening to proposals to revisit the way the testsuite is run and
better address the point above.
Something I've been thinking about is relying on Arquillian, similarly
to what the WFLY testsuite does. What's not trivial is the fact that we
still need to have different version of the Arquillian SPI
implementation (that is, different WFLY / EAP versions) used depending
on a maven profile specified when running the testsuite; moreover we
also need to be able to run against the result of building the latest
WFLY master (iow, not a released target for which a
wildfly-arquillian-container-xyz is available on the repository). We
could have custom server profile files (standalone-abc.xml) in the
jbossws sources for the supported containers to be used for starting
specific versions of the containers through Arquillian. The integration
tests could be split into groups meant to run against the various
different profiles of the selected target container. Pretty much
anything we need to customize on the server that can't be done using the
Deployer approach can actually be done through a proper profile file (I
would still keep the Deployer approach when working to limit the number
of profile files to maintain, as there's a lot of stuff in there).
Actually, we could even think about having a prepare phase before the
actual testsuite that runs given CLI scripts to obtain the desired
profile configuration.
Next steps
---------------
Please provide feedback / ideas. Then we need a plan and eventually
jiras created.
Cheers
Alessio
--
Alessio Soldano
Web Service Lead, JBoss
10 years, 7 months
New configuration options proposal
by Alessio Soldano
Folks,
I've been chatting with users and thinking a bit about the
client/endpoint descriptor-based configuration options we currently
offer in JBossWS. Looks like there's room for improvement, mainly to
allow setting stuff that is currently controlled through JBossWS /
Apache CXF APIs only. Hence, here is a proposal for few additions,
please have a look and let me know any comment.
* New client descriptor
----------------------------------------------------------------------
Currently we do have the jboss-webservices.xml descriptor on server
side; it allows setting options for endpoints included in the
deployment. For example, we can have properties specified in there,
which can affect the pre-defined endpoint config selection, some Apache
CXF features (policy alernative selection, just to say one), etc.
We don't have a corresponding client descriptor though. We could have a
default descriptor (say, jboss-webservices-client.xml) to be looked up
through TCCL when building JAX-WS client services. That would allow
setting properties for the specific client instead of at system/jvm
level; we already have properties for getting a specific pre-defined
client configuration, for controlling cxf bus selection, etc.
* Addition to the jboss-webservices.xml schema
----------------------------------------------------------------------
In jboss-webservices.xml we currently allow setting deployment level
properties. We should evaluate setting properties also at endpoint/port
level, basically within the port-component section.
* Apache CXF interceptors setup through properties
----------------------------------------------------------------------
Speaking of properties, currently specified in jboss-webservices.xml and
possibly in jboss-webservices-client.xml, we could start supporting two
additional props:
* org.apache.cxf.interceptor.InInterceptors, with the value string to be
parsed for getting a list of in-interceptor classnames; basically to
achieve the same we get with @InInterceptor
* org.apache.cxf.interceptor.OutInterceptors, with the value string to
be parsed for getting a list of out-interceptor classnames; basically to
achieve the same we get with @OutInterceptor
The interceptors would be attached either to the bus or to the
client/endpoint depending on where the property is declared.
Please provide feedback, so that we can possibly create jiras and
implement the relevant new features.
Cheers
Alessio
--
Alessio Soldano
Web Service Lead, JBoss
10 years, 11 months
JBossWS 4.3.1 release
by Alessio Soldano
Folks,
it's been several months since we released JBossWS 4.3.0.Final. The
JBossWS 5 development is still the priority and we're pretty much on
target at the moment; in the mean time, however, I thought it would make
sense to backport the most relevant bug fixes of the last few months to
the 4.3.x branch, so that we can cut a 4.3.1 release.
The up to date list of 4.3.1 issues is at:
https://issues.jboss.org/issues/?jql=project%20%3D%20JBWS%20AND%20fixVers...
The plan would be to release at some time between now and the end of
next week.
Cheers
Alessio
--
Alessio Soldano
Web Service Lead, JBoss
11 years, 1 month