Tapestry for Nonbelievers
A new article by I. Drobiazko and R. Zubairov introduces v. 5 of the Apache Tapestry component-oriented web framework. The tutorial shows how to create a component and covers IoC in Tapestry and Ajax.
Tracking change and innovation in the enterprise software development community
Posted by Bryan Clauser on Apr 11, 2008 11:57 PM
After 6 months of work, Spring Web Services 1.5.0 has been release. Based off contract-first development using SOAP service development, Spring-WS can be manipulated through XML to create document-driven Web services. Some of the highlights of the release include:
Two new transports: JMS and email, both for client and server
WSS4J-based WS-Security implementation, which allows for WS-Security on non-SUN JDKs (i.e. WebSphere) and JDK 1.4
WS-Addressing support for both client and server, supporting the August 2004 and final versions of the specification
Arjen Poutsma goes into detail about how some of the new features work, showing how these new changes can be implemented. There are examples of how to implement the new transports as well as an overview of some of the other features in this release. Aljern also provides feedback on design decisions and future functionality of Spring-WS.
Other feature include:
Spring-WS jars are now OSGi bundles,
A new, client-side interception mechanism, including WS-Security support,
@Endpoints are now @Components, so they are automatically picked up when using Spring 2.5 component scanning
The 1.5 release is 95% backwards compatible, and comment in the Spring forums have been positive when it comes to upgrading For a full list of the features in the release see the release announcement. Also see a recent InfoQ interview with Arjen Poutsma that goes more into detail about Spring-WS and some if its methodologies.
can this turn an osgi service in to a webservice? i.e. if i register an osgi service in the standard way, can spring turn that in to a webservice for me? if not, does anyone know something that can? thanks in advance.
can this turn an osgi service in to a webservice? i.e. if i register an osgi service in the standard way, can spring turn that in to a webservice for me?
No, Spring Web Services cannot turn a OSGi service into a Web Service. I currently know of no framework which can. In fact, I'm not so sure it's a good idea. OSGi services are plain classes, designed for local invocation, and thus have a fine-grained interface. The sweet spot for Web services is a course-grained interface, preferably designed in a contract-first fashion.
Apache Tuscany SCA supports this with the implementation.osgi and binding.ws extensions. If you'd like more info just ask on the mailing list and I'm sure someone would help get you going.
A new article by I. Drobiazko and R. Zubairov introduces v. 5 of the Apache Tapestry component-oriented web framework. The tutorial shows how to create a component and covers IoC in Tapestry and Ajax.
In this interview, Burton Group consultant Pete Lacey talks to Stefan Tilkov about his disillusionment with SOAP, his opinion on REST, and addresses some of the perceived shortcomings REST vs. WS-*.
Jay Fields presents his concept of Business Natural Languages - a type of Domain Specific Languages geared towards being readable by domain experts.
Adoption and interest for Distributed Version Control Systems is constantly rising. We will introduce the concept of DVCS and have a look at 3 actors in the area: git, Mercurial and Bazaar.
Deborah Hartmann interviewed Segundo Velasquez about his experience as customer with an Agile team during the initial phase of software design of a product.
David Cooksey shows how to fine grained versioning to a ClickOnce deployment using an HttpHandler written with ASP.NET, making partial rollouts to a test audience much easier.
Windows workflow (WF) is an excellent framework for implementing business processes, but lacks support for human activities. This article describes a completely generic approach for changing this.
In this interview taken during OOPSLA 2007, Markus Voelter talks about the importance of documenting the software architecture, and gives some good and also bad examples on how it could be done.
3 comments
Reply