WSO2 AppServer 2.0 - Web Service Mashups, Clustering


News: WSO2 AppServer 2.0 - Web Service Mashups, Clustering

  1. WSO2 has announced the release of their Web Services Application Server (WSAS) 2.0, which offers data services to expose relational data to external service consumers, offers a full set of WS-* specification-compatible services, and backward compatibility with Axis1. WSAS is able to be used within the context of an existing J2EE or Java EE server, or it can be used as its own full container (using Tomcat as the HTTP container in the standalone installation.) JAX-WS wasn't used for the services because JAX-WS doesn't provide the full range of services that a lower-level API such as Axis can provide, according to Sanjiva Weerawarana, CEO of WSO2. This wasn't a reflection on JAX-WS as an API, but more of an attempt to bring the most complete implementation possible to their audience. The design of WSO2 was meant to help move the specific declaration of services away from the code and into the container's arena. The primary features of this release:
    • Data services allow developers to expose data stored in relational databases in minutes via a Web services API—without programming. An XML response is generated using database data, making it fast and easy to include this data in Web mashups. Developers can deploy the data service configuration file directly or create a service using the UI wizard. WSAS 2.0 lets users take full advantage of the WS-* security stack to ensure data security.
    • Eclipse integration cuts the time to develop, deploy and debug Web services. It lets developers and administrators work in the familiar Eclipse environment, eliminating the need to have a deep understanding of the underlying Axis2 Web services. Wizard-based flows make it possible to automate most manual work.
    • Clustering and high availability are enabled by the most comprehensive open source management offering available. Configuration management for handling clusters of nodes includes load configuration, a deploy/undeploy service and functions for updating policies. WSAS 2.0 also features state replication for high availability, along with load balancing and failover.
    • Extended security with WSAS 2.0 includes full support for WS-Security, WS-Trust, WS-Policy and WS Conversation. Additionally XKMS support provides another means for developers to secure Web-based communications using public key infrastructure (PKI). An API is available for constructing XKMS messages based on the client side’s required service. Services are provided by XKMS service, which also handles the state space for protocol exchange.
    • EJB support makes it possible to expose EJBs as Web services. Developers can invoke operations on EJBs deployed on a remote J2EE application server (AS), use a graphical wizard to capture J2EE AS configuration details, and connect to J2EE AS using Java Naming Provider. Developers also can upload EJB Remote and Home interfaces from the wizard and deploy a Web service exposing EJB methods.
    • Axis1 backward compatibility allows enterprises to easily deploy any Apache Axis1-based Web service into WSAS 2.0 in order to engage advanced WS-* services, such as WS-RM and WS-Policy in front of their legacy services. In doing so, developers gain state-of-the-art WS-* functionality without having to rewrite their existing services.

    Threaded Messages (2)

  2. Why not support JAX-WS?[ Go to top ]

    Portability isn't at the top of everyone's list but for those who care why not give them a choice just as some of the others do (e.g.,CeltixFire)? Some might feel a tad uncomfotable with their applications remaining locked in what essentially will be a proprietary WSO2/Axisa programming model.
  3. JAX-WS support[ Go to top ]

    We have (nearly complete) JAX-WS support. We'll be doing a refresh with the certified JAX-WS support soon. Sanjiva.