JBoss.Net was born forking Axis, it was used for JBoss AS 3.x and then reached end of life. It was replaced by a new j2ee 1.4 compatible webservice stack (JBossWS) in 2006.
Later in 2008, the JBossWS Web Service Framework allowed us to properly use multiple webservice stacks on top of JBoss AS, one of them being Apache CXF.
Currently we maintain both JBossWS-Native and JBossWS-CXF, as well as supporting the former in EAP 4.x for years since the release (please get in touch with customer support for further details).
EAP 5 is going to provide support for both stacks instead.
As Mark said, given the current status, in the long term JBossWS-CXF will become the default JBoss WS stack, but that's not going to happen tomorrow.
Thank you for the quick history review. BTW, the reason I am asking is because I would like to work on web services and in particular for JBoss. I was just trying to select a path that will be useful in the long-term.
I've been looking at relevant JBoss code (the SPI and JBossWS-Native and also started looking at CXF and the JBossWS-CXF integration layer). I think I'll focus on CXF code for now.
OK. If you planning / considering contributing, please get in touch with me.