Wednesday, September 2, 2015

JBossWS 5.1.0.Final is available!

One month after the beta release, JBossWS 5.1.0 is eventually final!
This time, we have gone for a time-boxed release approach and limited the number of new features on top of previous release. The reason is that we really wanted the upcoming WildFly 10 to include the latest and greatest WS components. As a matter of fact, JBossWS 5.1.0 brings Apache CXF 3.1 series into the WildFly container; the latest Apache CXF versions, in turn, come with few performance improvements that we directly contributed to, while working on optimizing the whole WildFly WS stack.
On top of that and besides for a bunch of bug fixes, an interesting new feature has just been added to JBossWS 5.1, which is support for jboss-webservices.xml descriptor in EAR deployment archives. This allows setting a given behaviour of the stack for all sub-deployments included in an EAR archive packaged application, preventing the user from having to specify the same options in multiple jboss-webservices.xml descriptors.
You can have a look at the release notes for a list of the improvements and fixed issues.

JBossWS 5.1.0.Final is available for direct download and on both the JBoss and Maven Central repositories. The release documentation is here.

The supported target containers are WildFly 8.2.1.Final, WildFly 9.0.0.Final and WildFly 9.0.1.Final... and of course WildFly 10.0.0.CR1 and later will be including it by default already.

Thursday, August 6, 2015

JBossWS 5.0.1.Final and 5.1.0.Beta1

It's summer time, time for a break and for taking some rest... not really, as we released two new versions of JBossWS this week :-)

JBossWS 5.0.1.Final is a bug fix release, solving some issues that were found in the first version of the JBossWS 5 series. It also includes Apache CXF (3.0.6) and WSS4J upgrades that come with additional multiple fixes and security improvements. The target containers for JBossWS 5.0.1.Final are WildFly 9.0.0.Final as well as the recently released WildFly 8.2.1.Final and 9.0.1.Final.

JBossWS 5.1.0.Beta1 is the first milestone of the new webservices stack for WildFly 10, instead. While it drops support for Spring integration (jbossws-cxf.xml descriptor, which was not used a lot and causing confusion and problems), it eventually pulls the latest Apache CXF 3.1.x series. Of course, all the fixes in 5.0.1.Final are included in 5.1.0.Beta1 as well.
Additional new features are coming to 5.1.0 in the next months before it goes Final :-)

Summer time... time to get the latest JBossWS releases and give them a try ;-)

Friday, June 26, 2015

Migrating sources to GitHub

I've been asked multiple times why the JBossWS project sources were still hosted on a Subversion repository. I've also had to put up with the complaints on time-consuming checkouts and even a bit of mockery from someone for not having migrated to Git yet...
Anyway, last week I had some quiet days, got the inspiration and started the migration... so now the JBossWS sources are eventually hosted on GitHub :-)

I've started by creating a jbossws organization on GitHub. Since the JBossWS project is actually a collection of multiple components each having its own lifecycle, I decided to create a repository for each of them into the organization.
A proper migration requires importing the whole svn repository history, of course; the easiest approach to achieve that is to rely on the GitHub importer. The tool worked fine for me with the smallest repositories (for instance the jbossws-api and jbossws-spi ones), even if it took something like 2 hours for each import (but it's nice that you can let it run on background and be notified by email when the process is completed). Unfortunately, when letting the tool process big sections of the JBossWS Subversion repository (like the jbossws-cxf stack integration), weird import errors were eventually reported, so I had to figure out another way to perform the import.

The alternative approach that worked is based on git-svn. The first step is to build up a comprehensive author mapping file linking svn commit authors to GitHub users. I used the following bash command:

> svn log -q | awk -F '|' '/^r/ {sub("^ ", "", $2); sub(" $", "", $2); print $2" = "$2" <"$2">"}' | sort -u > authors-transform.txt

Then I created a local Git repository from the Subversion sources with the following command:

> git svn clone --stdlayout --no-metadata -A authors-transform.txt /tmp/rep

The process still takes multiple hours and fails if a not-mapped user commit is found, but when it's completed you have a copy of all sources in a local Git repository that is almost ready to push. Almost... as I still had to deal with tags because they're fetched the same as branches by the command above.
I moved to the /tmp/rep directory and started by adding a remote repository link and pushing the master:

> git remote add origin
> git push -u origin master

Then you'd have to manually create all the tags, but that's clearly unpractical if you have hundreds of them, so I googled a bit and ended up using the following two commands to generate the actual commands for pushing branches and tags respectively to the remote repository:

> printf "git push origin "; git show-ref | grep refs/remotes | grep -v '@' | grep -v remotes/tags | perl -ne 'print "refs/remotes/$1:refs/heads/$1 " if m!refs/remotes/(.*)!'; echo

> printf "git push origin "; git show-ref | grep refs/remotes/tags | grep -v '@' | perl -ne 'print "refs/remotes/tags/$1:refs/tags/$1 " if m!refs/remotes/tags/(.*)!'; echo

I only had to clean up the output of the first command a bit as the trunk branch was clearly not to be pushed (it's the master pushed previously) and I actually did not want to push some stale branches.
After having iterated the process above for all JBossWS components that failed the automatic import process, I finally had all the sources there at GitHub.

The final steps were to disable the issue tracker & wiki on GitHub (we already use JIRA and have an equivalent to the wiki at and to invite proper users to join the Owner group for the organization as well as other specific groups that were needed.

A day was later spent on updating the continuous integration build environment and the project home page to point to the new repositories... but that's not that interesting to be described in details here ;-)

Enjoy the new repos, fork JBossWS and feel free to submit pull requests with your patches!

Monday, April 27, 2015

JBossWS 5.0.0.Final is available!

I'm happy to announce that JBossWS 5.0.0.Final is out!
The release comes with lots of new features and bug fixes. To get an idea of the new functionalities you can have a look at previous posts here, here and here.
Besides for the upgrade to Apache CXF 3 series, which brings a lot of new and interesting features, this release mainly focuses on providing simplified configurations options to the user. In particular:
With the above items (as well as other new functionalities) covering most of the scenarios in which users would have needed Spring based descriptors, the JBossWS integration with Spring is now declared deprecated.

It's now time for you to download JBossWS 5.0.0.Final, install and give it a try! Feedback is welcome as usual!

The documentation is included in the release (together with the sample testsuite) and is also available at in its latest version.
The supported target containers for this release are WildFly 8.0.0.Final, WildFly 8.1.0.Final and WildFly 8.2.0.Final. The current WildFly master has also been updated to the new WS components so that future WildFly releases will come with it.
Have fun :-)

Tuesday, March 24, 2015

Moving towards JBossWS 5...

Even if I've been silent here lately, my team is actively working on JBossWS 5 and we're getting closer to the first non-Beta release.

The first Beta release (JBossWS 5.0.0.Beta1) was tagged in September last year; it brought Apache CXF 3 series in JBossWS / WildFly and eventually dropped JAX-RPC support ;-)

JBossWS 5.0.0.Beta2 was tagged a couple of months later and featured improvements in the pre-defined client/endpoint configuration area and the options for declaring Apache CXF interceptors through simple configuration properties.

The latest Beta release so far, JBossWS 5.0.0.Beta3, has been tagged and integrated in current WildFly master last month; the most notable change in it is the completely new build and testsuite framework, which now fully relies on Arquillian and ShrinkWrap for WS endpoints testing.

More interesting additions, in the direction of enabling configuring Apache CXF proprietary features without recurring to Spring descriptors, have already been implemented and are coming soon.

Now, you're welcome to go, checkout JBossWS 5.0.0.Beta3 tag and play with it. Or you can simply hack on the latest WildFly master. (also note that WildFly 9 Beta1 is being released very soon!)
Alternatively, you could also play with another recent WS release, the 1.1.0.Beta1 version of the our jaxws-codefirst Maven Archetype, which has just been moved to rely on JBossWS 5 Beta artifacts. You can read about it in a previous post of mine, but it basically boils down to simply using the following command line to kick start a WS project in few seconds:
mvn archetype:generate

That's all for now, stay tuned, JBossWS 5 is coming... :-)

Tuesday, September 23, 2014

A book on JAX-WS in WildFly and more...

It was last winter when I was offered to author a book on the Web Services stack provided by JBossWS / Apache CXF in WildFly. I eventually took up the challenge and invested part my spare time on writing the book.
To be honest, what really inspired me was the chance of finally being able to write down from scratch how I believe a user should approach the Web Services world and move on from the theory to real world usage scenarios.
As a matter of fact, throughout the years I spent contributing and leading the JBossWS project, I've often had to deal with users picking up concepts and code snippets from books here and there and then asking why they were not achieving what they expected in JBoss AS / WildFly. This opportunity looked like a way to eventually say "look, if you really don't want to read and understand the project documentation, here is a book that likely has all you need and nothing more" ;-)
The goal was probably a bit too ambitious, nevertheless I believe the result of my effort is definitely good.
So, if you want to get your hands on my JAX-WS book, it's currently available in electronic edition at and on Amazon. Printed edition coming soon.

Tuesday, September 16, 2014

How to kick start a WS project in few seconds

One of the goals I committed to when I joined the JBoss Web Services project back in 2007 was to improve the JBossWS tooling offer and possibly make the users' life easier when they have to deal with WS technologies.
Some of the solutions we developed in this area during the past years are now surpassed, others are still here and being used (as an example, think about the Wise project, which gets very limited attention from us due to lack of time, but currently powers the Web Service Tester within JBoss Tools, just to say).
In the last years Maven has been adopted as the de-facto standard solution for building projects; as a consequence, the JBossWS team made available a couple of Maven plugins for running its JAX-WS tools (wsconsume and wsprovide). As part of a customer project build it is hence possible to automatically generate a JAX-WS client or Service Endpoint Interface from a given WSDL contract and viceversa.
In February last year, with the aim of further clarifying how the plugins could be leveraged in final user projects, I wrote a post on the forum describing an example of the above mentioned Maven plugins.
The next step was to simplify the sample project creation and that's what has been eventually addressed. The JBossWS project now features a custom Maven Archetype, basically a WS-enabled project template toolkit.
Whenever a user needs to start a new project aiming at providing and/or consuming a JAX-WS endpoint, the new jaxws-codefirst archetype allows creating a starting project (including working build and sample helloworld client and endpoint) in few seconds. It's simply a matter of issuing a command and replying to simple questions on the desired artifact and group ids for the project being generated:

mvn archetype:generate

The generated project includes:
  • a sample HelloWorld code-first POJO endpoint
  • an integration test that gets the WSDL contract for the above service, builds up a client and invokes the endpoint
  • a pom.xml for creating a war archive; the project has proper WS component dependencies and uses both wsprovide and wsconsume maven plugins for generating the contract for the code-first endpoint and then generating the client stubs for such contract
  • a plugin for deploying the archive on WildFly.
The project is built and tested by simply running:

mvn wildfly:deploy
mvn integration-test

The build processes the various plugins and calls into the JBossWS tools to generate all the required classes for building the deployment archive and client. The user can test the sample, have a look at the project structure and then either trash the sample endpoint and testcase and replace them with his own components, or modify them step-by-step to achieve what he needs. No need to start from scratch anymore :-)
A 1.0.0.Beta1 version of the archetype is currently available; it relies on JBossWS 4.2.3.Final and is out there for early testers. I've been fixing few bugs on it recently and the plan is to release a new version, based on JBossWS 5, together with the next release of the webservices stack. So give it a try and send us your feedback; we'll try to fix any issue before the release.