JAX-WS

JAX-WS
Name	JAX-WS
Title	JAX-WS
Developer	Sun Microsystems; Oracle Corporation
Released	2006
Latest release version	(varies by implementation)
Programming language	Java
Operating system	Cross-platform
Platform	Java Platform, Standard Edition; Java Platform, Enterprise Edition
License	GPL; CDDL; proprietary (varies)

JAX-WS Java API for XML Web Services is a Java-based API for creating and consuming SOAP-based Web services that integrates with Java SE and Java EE platforms. It builds on standards such as SOAP, WSDL 1.1, XML Schema, and WS-I profiles and was developed originally by Sun Microsystems and later maintained by Oracle Corporation with implementations in multiple runtime projects. JAX-WS is widely used in enterprise systems alongside technologies from vendors like IBM, Red Hat, Apache Software Foundation, and Microsoft.

Overview

JAX-WS provides a programming model for building SOAP web services on the Java Platform, Standard Edition and Java Platform, Enterprise Edition, enabling integration with enterprise systems such as SAP SE, Salesforce, Oracle Database, and IBM Db2. It supports annotations from Java SE 6 onward and interoperates with standards bodies and profiles including W3C, OASIS, and WS-I Basic Profile. Implementations appear in projects and products from Apache Software Foundation (Apache CXF), Eclipse Foundation (Metro), GlassFish, WildFly, and proprietary stacks from IBM WebSphere, Oracle WebLogic Server, and Microsoft Azure tooling.

Architecture and Components

The architecture uses service endpoint interfaces (SEIs), bindings, and runtime handlers to map between Java and SOAP artifacts; components are often provided by containers such as GlassFish and application servers like WildFly and Oracle WebLogic Server. Key components include the proxy/stub generation tools, runtime dispatchers, SOAP handlers, and message routers, which interact with protocols and formats specified by WSDL 1.1, SOAP 1.1, SOAP 1.2, and XML Schema. Security and reliability extensions may rely on specifications from OASIS, WS-Security, WS-ReliableMessaging, and WS-Addressing, and are implemented in stacks from Apache CXF, Metro, IBM WebSphere Application Server, and Red Hat JBoss.

Programming Model and APIs

Developers use annotations like javax.jws.WebService and javax.jws.WebMethod to define service endpoints, and tools such as wsimport and wsgen to generate client proxies and artifacts; these tools are provided in Java SE toolkits and vendor SDKs from Oracle Corporation and IBM. The model supports both contract-first (WSDL-first) and code-first (annotations-first) approaches, interoperating with tooling from Eclipse IDE, NetBeans, IntelliJ IDEA, and build systems like Apache Maven and Gradle. Data binding integrates with technologies such as JAXB (from GlassFish and Eclipse Project), and alternative bindings are available via XMLBeans and Aegis in stacks like Apache Axis2 and Apache CXF.

Development and Deployment

Typical development flows involve generating artifacts with wsimport, implementing SEIs, configuring handlers and features, and packaging as Java ARchive or Enterprise Archive for deployment to application servers such as GlassFish, Oracle WebLogic Server, IBM WebSphere Application Server, WildFly, or cloud platforms including Amazon Web Services, Microsoft Azure, and Google Cloud Platform. Continuous integration and delivery pipelines often use Jenkins, GitLab CI/CD, Travis CI, and container orchestration via Kubernetes and Docker images supplied by vendors like Red Hat and Oracle.

Interoperability and Standards Compliance

Interoperability is achieved by adhering to W3C and OASIS standards — examples include WSDL 1.1, SOAP 1.1, SOAP 1.2, XML Schema Definition, and profiles from WS-I. Major vendor implementations certify against WS-I Basic Profile test suites from organizations such as OASIS and the World Wide Web Consortium. Interop testing events and initiatives by OASIS, WS-I, Eclipse Foundation, and vendor consortia (including IBM, Oracle, Microsoft, SAP SE) help ensure cross-platform compatibility with stacks like Apache CXF, Metro, Apache Axis2, and proprietary servers.

Performance and Security Considerations

Performance tuning involves message optimization, MTOM support, and connection management; features are implemented in servers such as Oracle WebLogic Server, IBM WebSphere Application Server, GlassFish, and middleware from Red Hat. Security is achieved via WS-* standards like WS-Security, SAML assertions from OASIS, X.509 certificates from IETF PKI standards, and transport-layer TLS as defined by IETF; implementations integrate with LDAP directories, Keycloak, Active Directory from Microsoft Corporation, and hardware security modules from vendors like Thales Group. Performance comparisons and tuning guides often reference benchmarking on platforms including SPEC, Java Microbenchmark Harness, and vendor whitepapers from Oracle Corporation and IBM.

History and Implementations

JAX-WS was introduced as part of the Java Community Process and the JSR 224 family of specifications; its development involved contributors from Sun Microsystems, Oracle Corporation, IBM, and the wider Java community. Notable implementations include Metro (originally from Sun Microsystems and later part of Eclipse Foundation), Apache CXF from the Apache Software Foundation, Apache Axis2, and commercial offerings bundled with Oracle WebLogic Server, IBM WebSphere, and Red Hat JBoss EAP. The API evolved alongside Java releases and standards activities involving W3C, OASIS, and the WS-I organization, and it remains supported in many enterprise JVMs and cloud middleware stacks.

Category:Java APIs