The JBossWS project is being presented through a talk at JBUG Munich next week (Monday, May 16th).
The presentation is going to be focussed on the recent JBossWS - Apache CXF integration efforts as well as on the future of the project.
More details on the JBUG Munich website.
Wednesday, May 11, 2011
JBossWS 4.0.0.Beta1 is out!
After months of active development, the first Beta release of JBossWS 4 is finally out!
The main target of JBossWS 4 is in supporting the upcoming JBoss Application Server 7 and contributing to the innovation that's coming with it.
For instance, AS7 comes with a new modular classloading and requires proper isolation between user classes and JBoss implementation details. As a consequence we've gone through a complete review of ws integration classloading details, re-defined the JBossWS public API and really cleaned up a bunch of things all over the WS components. Full documentation is coming with the next beta releases, however a FAQ for WS AS7 usage is already available.
The JBossWS-CXF stack was also moved to including the recent Apache CXF 2.4 release. The integration has been completely reviewed as CXF 2.4 is less bound to Spring, hence allowing JBossWS to avoid most of the tricks that were in place before to support some "non-Spring" scenarios.
Apache CXF 2.4 also includes many new features and improvements in the WS-Security area. Adding this to some additional integration work on @EndpointConfig annotation, we're finally able to support a completely "Spring-free" WS-SecurityPolicy scenario, with signature / encryption / username token based authentication (sources, resources).
Finally, mainly because of the AS 7 improvements, in terms of performance handling ws invocations, the current JBoss AS 7 + JBossWS 4 integration is up to 35% faster then JBoss AS 6 Final + JBossWS 3.4.1.GA
The Beta1 artifacts are available on the JBoss Maven repository, sources can be retrieved from SVN repository as usual.
While JBoss AS 7 is meant to be the primary (and probably only, once we reach final stage) target of JBossWS 4.x, at the moment JBoss AS 6 Final is also supported as target container.
Please note that given the AS7 is currently in very active development phase, JBossWS 4.0.0.Beta1 is fully tested against its current (today, May 11) version only. As soon as JBoss AS 7 will reach CR level, we'll add that release to the released supported target containers list of JBossWS 4.
Please have a look at the first Beta of JBossWS 4, feedback is always welcome!
The main target of JBossWS 4 is in supporting the upcoming JBoss Application Server 7 and contributing to the innovation that's coming with it.
For instance, AS7 comes with a new modular classloading and requires proper isolation between user classes and JBoss implementation details. As a consequence we've gone through a complete review of ws integration classloading details, re-defined the JBossWS public API and really cleaned up a bunch of things all over the WS components. Full documentation is coming with the next beta releases, however a FAQ for WS AS7 usage is already available.
The JBossWS-CXF stack was also moved to including the recent Apache CXF 2.4 release. The integration has been completely reviewed as CXF 2.4 is less bound to Spring, hence allowing JBossWS to avoid most of the tricks that were in place before to support some "non-Spring" scenarios.
Apache CXF 2.4 also includes many new features and improvements in the WS-Security area. Adding this to some additional integration work on @EndpointConfig annotation, we're finally able to support a completely "Spring-free" WS-SecurityPolicy scenario, with signature / encryption / username token based authentication (sources, resources).
Finally, mainly because of the AS 7 improvements, in terms of performance handling ws invocations, the current JBoss AS 7 + JBossWS 4 integration is up to 35% faster then JBoss AS 6 Final + JBossWS 3.4.1.GA
The Beta1 artifacts are available on the JBoss Maven repository, sources can be retrieved from SVN repository as usual.
While JBoss AS 7 is meant to be the primary (and probably only, once we reach final stage) target of JBossWS 4.x, at the moment JBoss AS 6 Final is also supported as target container.
Please note that given the AS7 is currently in very active development phase, JBossWS 4.0.0.Beta1 is fully tested against its current (today, May 11) version only. As soon as JBoss AS 7 will reach CR level, we'll add that release to the released supported target containers list of JBossWS 4.
Please have a look at the first Beta of JBossWS 4, feedback is always welcome!
Subscribe to:
Posts (Atom)