It's been a week of JBoss / Red Hat web services presentations in the North Italy area.
As mentioned in the previous blog entry, Red Hat has been sponsoring ECOWS 2011, this year's edition of the European Conference on Web Services. I've taken a session in the industry track; the audience seems to have appreciated the Red Hat involvement in the web services area, especially the contribution with the standardization bodies. The slides for my presentation are available online.
Today I've joined the first meeting of the Milan JBoss User Group and presented on the webservices subsystem of JBoss Application Server 7. Take a look at slides and get involved with the JBUG, interesting meetings are being planned for the future.
Tuesday, September 20, 2011
Wednesday, September 7, 2011
JBoss at ECOWS 2011
The European Conference on Web Services (ECOWS) is the premier conference series for both researchers and practitioners to discuss the latest advances in the state of the art and practices of Web services and to foster cross-European collaboration and exchange. The 9th edition of the ECOWS series will be held on September 14-16 at the University of Lugano, Switzerland.
JBoss / Red Hat is supporting ECOWS 2011 as silver sponsor.
I'll be attending the conference and presenting on the JBoss involvement in the webservice area.
The agenda for the event covers multiple tracks, including both research and industry interesting talks.
JBoss / Red Hat is supporting ECOWS 2011 as silver sponsor.
I'll be attending the conference and presenting on the JBoss involvement in the webservice area.
The agenda for the event covers multiple tracks, including both research and industry interesting talks.
Wednesday, August 31, 2011
Apache CXF PMC
Just a quick note to say that I've recently been offered to join the Apache CXF PMC and I accepted.
A project management committee (PMC) is a committee of the Apache Software Foundation charged with responsibility for a top level project. The PMC is the vehicle through which decision making power and responsibility for oversight is devolved to developers.
I'm of course proud of taking part to Apache CXF decisions and will do my best. Thanks to Dan and the other members for the trust.
A project management committee (PMC) is a committee of the Apache Software Foundation charged with responsibility for a top level project. The PMC is the vehicle through which decision making power and responsibility for oversight is devolved to developers.
I'm of course proud of taking part to Apache CXF decisions and will do my best. Thanks to Dan and the other members for the trust.
Thursday, July 28, 2011
Publishing WS endpoints through AS7 services
JBoss AS 7.0.0 Final has been released and is available to the community, so we're currently working on the 7.1.0 version of the application server, which is coming with many webservices functionalities additions. While most of them will be aim at covering JCP specification requirements (mainly JSR-109 and JSR-101), some management and general use new features are also coming soon.
Recently it's been the turn of JBoss XTS for being integrated in JBoss AS 7.
XTS provides transaction support for web services, implementing WS-AtomicTransaction and WS-BusinessActivity specifications. In order for providing such functionalities, XTS needs to start a given number of WS endpoints to take part into the transactions management. According to the JBoss AS 7 design, this is to be achieved using JBoss AS 7 services.
Publishing a WS endpoints on JBoss AS7 was previously directly bound to the processing of a given deployment unit having webservices endpoint implementation classes in it. So the required steps for achieving our goal were:
We ended up with a solution that might appear pretty much equivalent to the JAX-WS Endpoint.publish(..) API at first sight, except it
The XTS integration easily leveraged the new JBossWS feature, installing and setting up dependencies on multiple WS endpoint publisher services.
You can have a look at this by checking out the latest JBoss AS 7 master from github and starting the standalone-xts.xml profile. During the boot, XTS subsystem and its 14 required WS endpoints are concurrently started in something like 2.5s on a my mid-level laptop ;-)
If you're writing your own AS7 component and need publishing a WS POJO endpoints as part of that, consider giving this new feature a try.
Recently it's been the turn of JBoss XTS for being integrated in JBoss AS 7.
XTS provides transaction support for web services, implementing WS-AtomicTransaction and WS-BusinessActivity specifications. In order for providing such functionalities, XTS needs to start a given number of WS endpoints to take part into the transactions management. According to the JBoss AS 7 design, this is to be achieved using JBoss AS 7 services.
Publishing a WS endpoints on JBoss AS7 was previously directly bound to the processing of a given deployment unit having webservices endpoint implementation classes in it. So the required steps for achieving our goal were:
- abstracting the endpoint publish process away from the deployment processing; that was possible thanks to the already existing convenient split of JBossWS endpoint publish logic into deployment aspect blocks, completely hidden behind the JBossWS SPI (iow the JBossWS internals do not directly rely on JBoss AS classes)
- defining a simple API for publishing POJO endpoints given the endpoint class names, classloader and publish address
- providing a JBoss AS7 implementation for such an API
- serving that through an AS7 service
We ended up with a solution that might appear pretty much equivalent to the JAX-WS Endpoint.publish(..) API at first sight, except it
- allows for publishing an endpoint to the HTTP server of the currently running JBoss AS 7 instance
- is embedded into a JBoss AS 7 service, allowing efficient, concurrent and perhaps even lazy/on-demand start/stop of endpoints as part of AS7 operations (for instance, the boot)
The XTS integration easily leveraged the new JBossWS feature, installing and setting up dependencies on multiple WS endpoint publisher services.
You can have a look at this by checking out the latest JBoss AS 7 master from github and starting the standalone-xts.xml profile. During the boot, XTS subsystem and its 14 required WS endpoints are concurrently started in something like 2.5s on a my mid-level laptop ;-)
If you're writing your own AS7 component and need publishing a WS POJO endpoints as part of that, consider giving this new feature a try.
Thursday, July 7, 2011
JBoss AS 7 webservices features
JBoss Application Server 7 is highly configurable and allows for running different profiles, including one or more subsystems. The optional webservices subsystem is based on JBossWS-CXF 4.x.
JBoss AS7 users can turn on full webservices capabilities by enabling the org.jboss.as.webservices module extension and the webservices subsystem in their standalone.xml / domain.xml descriptors:
On JBoss AS 7 Final, the webservices extension / subsystem is already enabled and available in a separate domain configuration, domain-preview.xml / standalone-preview.xml. Users can run a given server configuration as follows:
Once the webservices capabilities are enabled, basic JAXWS features as well as advanced WS-* functionalities are available.
The JBossWS 4.x documentation covers all the details, including full JAXWS user guide , JAXWS tooling and quick start sections.
Moreover, examples are also provided on advanced topics:
JBoss AS7 users can turn on full webservices capabilities by enabling the org.jboss.as.webservices module extension and the webservices subsystem in their standalone.xml / domain.xml descriptors:
<server name="foo" xmlns="urn:jboss:domain:1.0">
<extensions>
[...]
<extension module="org.jboss.as.webservices"/>
[...]
</extensions>
[...]
<profile>
[...]
<subsystem xmlns="urn:jboss:domain:webservices:1.0" xmlns:javaee="http://java.sun.com/xml/ns/javaee" xmlns:jaxwsconfig="urn:jboss:jbossws-jaxws-config:4.0">
<wsdl-host>localhost</wsdl-host>
<modify-wsdl-address>true</modify-wsdl-address>
</subsystem>
[...]
</profile>
[...]
</server>
On JBoss AS 7 Final, the webservices extension / subsystem is already enabled and available in a separate domain configuration, domain-preview.xml / standalone-preview.xml. Users can run a given server configuration as follows:
./bin/standalone.sh -server-config standalone-preview.xml
Once the webservices capabilities are enabled, basic JAXWS features as well as advanced WS-* functionalities are available.
The JBossWS 4.x documentation covers all the details, including full JAXWS user guide , JAXWS tooling and quick start sections.
Moreover, examples are also provided on advanced topics:
Wednesday, May 11, 2011
JBossWS @ JBUG München
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.
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.
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)