In addition to its leadership role in standards bodies, BEA implements the latest Web Services standards into the platform including SOAP, WSDL, and UDDI.

Web Services Atomic Transaction (WS-AtomicTransaction) - Version 1.0
This specification the definition of the atomic transaction coordination type that is to be used with the extensible coordination framework described in the WS-Coordination specification. The specification defines three specific agreement coordination protocols for the atomic transaction coordination type: completion, volatile two-phase commit, and durable two-phase commit.

Web Services Business Activity Framework (WS-BusinessActivity) - Version 1.0
This specification provides the definition of the business activity coordination type that is to be used with the extensible coordination framework described in the WS-Coordination specification. The specification defines two specific agreement coordination protocols for the business activity coordination type: BusinessAgreementWithParticipantCompletion, and BusinessAgreementWithCoordinatorCompletion. Developers can use any or all of these protocols when building applications that require consistent agreement on the outcome of long-running distributed activities.

Web Services Coordination (WS-Coordination) - Version 1.0
This specification describes an extensible framework for providing protocols that coordinate the actions of distributed applications. Such coordination protocols are used to support a number of applications, including those that need to reach consistent agreement on the outcome of distributed activities.

Web Service Transfer (WS-Transfer)
This specification describes a general SOAP-based protocol for accessing XML representations of Web service-based resources.

Web Services for Remote Portlets (WSRP) Version 1.0
This specification defines web services for aggregating portlets and content from remote applications. These web services are used by portals to aggregate remote portlets into portal pages, thereby enabling large-scale portal deployments to decouple their portlets from the portal deployment.

Web Services for Remote Portlets 1.0 Primer
This primer discusses the WSRP 1.0 specification from an implementation point of view, and helps advanced users understand and troubleshoot the WSRP protocol.

Web Services Trust Language (WS-Trust)
This specification defines extensions that build on [WS-Security] to provide a framework for requesting and issuing security tokens, and to broker trust relationships.

Web Services Secure Conversation Language (WS-SecureConversation)
This specification defines extensions that build on [WS-Security] and [WS-Trust] to provide secure communication across one or more messages. Specifically, this specification defines mechanisms for establishing and sharing security contexts, and deriving keys from established security contexts (or any shared secret).

Web Services Metadata Exchange
This specification (WS-MetadataExchange) defines messages to retrieve specific types of metadata associated with an endpoint.

BPEL and BPELJ
Get the latest information on BPEL and BPELJ, two related business process standardization efforts supported by BEA, learn more...

Web Services Business Activity Framework
The (WS-BusinessActivity) specification provides the definition of the business activity coordination type that is to be used with the extensible coordination framework described in the WS-Coordination specification. The specification defines two specific agreement coordination protocols for the business activity coordination type: BusinessAgreementWithParticipantCompletion, and BusinessAgreementWithCoordinatorCompletion. Developers can use any or all of these protocols when building applications that require consistent agreement on the outcome of long-running distributed activities. The March 2004 version is available here.

Web Services Dynamic Discovery
The WS-Discovery specification defines a multicast-based ad-hoc discovery protocol to locate available Web services. This enables clients on a network to automatically find Web services.

Web Services Eventing
This Web Services Eventing (WS-Eventing) specification proposes a way of communicating about events within and between Web services. The updated specification incorporates industry feedback generated from ongoing feedback and interoperability workshops and reflects progress on quality and interoperability.

Web Services Coordination
This is the November 2004 version of WS-Coordination. The Web Services Coordination (WS-Coordination) specification describes an extensible framework for providing protocols that coordinate the actions of distributed applications. Such coordination protocols are used to support a number of applications, including those that need to reach consistent agreement on the outcome of distributed transactions. The September 2003 version is still available here, and the August 2002 version is available here.

Web Services Transaction
The combined Web Services Transaction (WS-Transaction) specification is now divided into WS-AtomicTransaction and WS-BusinessActivity. These specifications describe coordination types that are used with the extensible coordination framework described in the WS-Coordination specification.

Developers can use either or both of these coordination types when building applications that require consistent agreement on the outcome of distributed activities.

The September 2003 version of WS-AtomicTransaction is still available here. The August 2002 combined version is still available here.

Web Services Federation Language (WS-Federation)
The Web Services Federation Language (WS-Federation) specification defines mechanisms to allow different security realms to federate, such that authorized access to resources managed in one realm can be provided to security principals whose identities and attributes are managed in other realms. This includes mechanisms for brokering of identity, attribute, authentication and authorization assertions between realms, and privacy of federated claims.

XML, SOAP and Binary Data
The XML, SOAP and Binary Data specification discusses the architectural issues encountered when using opaque non-XML data in XML applications, including (but not limited to) Web services and SOAP.

SOAP Messages with Attachments
The SOAP Messages with Attachments specification defines a small number of XML and SOAP conventions that clarify an earlier proposal and collectively allow opaque data and web references to be used in an Infoset-based messaging model.

Web Services Addressing Specification
The Web Service Addressing (WS-Addressing) specification provides transport-neutral mechanisms to address Web services and messages. Specifically, this specification defines XML elements to identify Web service endpoints and to secure end-to-end endpoint identification in messages. This specification enables messaging systems to support message transmission through networks that include processing nodes such as endpoint managers, firewalls, and gateways in a transport-neutral manner.

Web Services Reliable Messaging Protocol
The Web Services Reliable Messaging (WS-ReliableMessaging) specification describes a protocol that allows messages to be delivered reliably between distributed applications in the presence of software component, system, or network failures. The protocol is described in this specification in an independent manner allowing it to be implemented using different network transport technologies. To support interoperable Web services, a SOAP binding is defined within this specification.

Web Service Acknowledgement Protocol
The Web Service Acknowledgement Protocol (WS-Acknowledgement) specification is designed to support reliable message exchange between services by providing for at-least-once and exactly-once SOAP message transfer guarantees. enable WS-Acknowledgement senders to request explicit acknowledgement from WS-Acknowledgement receivers that a WS-Acknowledgement Request Message has been received.

Web Service CallBack Protocol
The Web Service CallBack Protocol (WS-CallBack) specification consists of the CallBack SOAP header and an associated WSDL definition. WS-CallBack is used to dynamically specify where to send asynchronous responses to a SOAP request.

Web Services Message Data
The Web Services Message Data (WS-MessageData) specification introduces the MessageData header, which enables the re-use of meta-data about a message across SOAP extensions. As new types of message meta-data are standardized it is hoped that they will be placed inside of the MessageData header so as to more easily enable re-use.

Web Services Policy Framework
The Web Services Policy Framework (WS-Policy) provides a general-purpose model and corresponding syntax to describe and communicate the policies of a Web Service. WS-Policy defines a base set of constructs that can be used and extended by other Web Services specifications to describe a broad range of service requirements, preferences, and capabilities.=

Web Services Policy Assertions Language
The Web Services Policy Assertions Language (WS-PolicyAssertions) specifies a set of common message policy assertions that can be specified within a policy. The specification defines general messaging-related assertions for use with WS-Policy.

Web Services Policy Attachment
The Web Services Policy Attachment (WS-PolicyAttachment) specifies three specific attachment mechanisms for using policy expressions with existing XML Web service technologies. Specifically, it defines how to associate policy expressions with WSDL type definitions and UDDI entities. It also defines how to associate implementation-specific policy with all or part of a WSDL portType when exposed from a specific implementation.

WSCI
The new Web Service Choreography Interface (WSCI) is an XML-based interface description language that describes the flow of messages exchanged by a Web Service participating in choreographed interactions with other services.
The WSCI 1.0 specification was codeveloped by BEA Systems, Intalio, SAP AG, and Sun Microsystems. An abstract of the specification, full copies of the specification in HTML and PDF formats, a FAQ, and a feedback form are available here.

SOAP
BEA includes an implementation of both the SOAP 1.1 and SOAP 1.1 with Attachments specifications to support both RPC-style Web Services and Message-style Web Services. BEA also provides a servlet-based SOAP implementation that integrates with stateless session beans and JMS.
SOAP invocations can be mapped to a stateless session bean method or cause a JMS message to be produced for consumption by a JMS listener, such as a message-driven bean.

A new SOAP specification is available: SOAP Conversation (SOAP-Conversation) is a SOAP- and WSDL-based specification that defines long-running and asynchronous interactions between SOAP-based senders and receivers. View the spec and send us your feedback.

SOAP Over UDP
This specification defines a binding for SOAP envelopes to user datagrams. View the spec.

WSDL
WebLogic Server automatically generates WSDL for stateless EJBs and JMS.
The generated WSDL is accessible and downloadable from user-defined URLs to support publishing and retrieval of Web Services. In addition, a stubbed out EJB or JSP can be generated from any WSDL hosted externally or internally.

UDDI
BEA provides the facilities to connect to a private or public UDDI registry, navigate through the descriptions given in the registry, select specific methods and generate a portlet (portal window), JSP code and so on. This utility can be a used as stand-alone module leveraged by the application frame work or incorporated into BEA's portal framework.

(BTP) Business Transaction Protocol
BEA has offered its Business Transaction Protocol (BTP) to accelerate the adoption of open industry standards and facilitate large-scale business-to-business (B2B) deployments worldwide. BTP is already delivered as a key enabling technology at BEA and is the basis for this standardization initiative.

The BTP specification provides a much-needed addition to the infrastructure community. It's support among transaction managers will provide flexibility not currently available within XA-compliant, two phase commit transaction engines.

Get the details here