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!
JBossWS 5.4.0.FInal is released !
I am pleased to annouce JBossWS 5.4.0 Final is out. In this release we upgraded many components as usual and brings Elytron client configur...
-
After some micro bug fix releases on the 5.1 stream, JBossWS 5.2.0.Final has eventually been released . The latest versions brings a lot o...
-
JBoss Application Server 7 is highly configurable and allows for running different profiles , including one or more subsystems . The optio...
-
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 poss...
8 comments:
Is there a binary distribution available like the ones available for the 3.4.1 release? as I'm not sure what I need to use from the maven repository to update my JBoss6 install.
Stephen,
no, there's not an already built binary distro available, as that's a Beta release. You can get the sources from svn and install to JBoss AS 6 using the build.
http://anonsvn.jboss.org/repos/jbossws/stack/cxf/tags/jbossws-cxf-4.0.0.Beta1/
Hi,
I'm trying to install the beta release on JBoss AS6 but an error occurs while I run build.
The error is:
mvn-settings:
[exec] [INFO] Scanning for projects...
[exec] [ERROR] The build could not read 1 project -> [Help 1]
[exec] [ERROR]
[exec] [ERROR] The project org.jboss.ws.cxf:jbossws-cxf:4.0.0.Beta2 (C:\Users\emanuel.braga\workspace\jbossws-cxf-4.0.0.Beta2\pom.xml) has 1 error
[exec] [ERROR] Non-resolvable parent POM: Failure to find org.jboss.ws:jbossws-parent:pom:1.0.10.Alpha1 in http://repo1.maven.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced and 'parent.relativePath' points at wrong local POM @ line 25, column 11 -> [Help 2]
[exec] [ERROR]
[exec] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[exec] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
[exec] [ERROR]
[exec] [ERROR] For more information about the errors and possible solutions, please read the following articles:
[exec] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[exec] [ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
Any help?
Thanks.
geek 001,
did you properly configure your maven repositories? http://community.jboss.org/wiki/JBossWS-Mavenization/#Create_or_Update_Maven_2_Settings_JBoss_Nexus_Maven_Repository
Yes, It was it.
Thanks a lot. :)
Hi Alessio,
Sorry to bother you again. I've successfully upgraded JBoss AS6 with Beta2 of JbossWS-CXF. Now, while building the JEE project, it is thrown an exception saying that wsimport can not be found.
Is this normal? What can I do to resolve this issue?
Thanks again.
geek01, you might want to post on the jbossws user forum if you didn't yet.
The full exception might help.
Hi Alessio,
I've posted @ http://community.jboss.org/thread/169861
Thanks one more time.
Post a Comment