Package org.ws4d.java.communication

This package defines the communication protocol within the JMEDS framework.

See:
Description

Interface Summary

Bindable	This interface supports usage and management of communication bindings.
CommunicationBinding	This interface enables Bindings for communication.
CommunicationManager	The * NEW * communication manager interface.
CommunicationUtil
DiscoveryBinding	This interface enables Bindings for discovery communication.
IncomingMessageListener	Used to register interest for incoming (request) messages of a certain type.
ProtocolDomain
RequestHeader
Resource	This is the interface for resources which can be deployed by a given communication manager.
ResponseCallback	This interface is used to receive answers to request messages sent via CommunicationManager#send(Message, ProtocolDomain, ResponseCallback) .
ResponseHeader

Class Summary

CommunicationManagerRegistry
ContextID	An ID for a context (Primary for MIME context).
DefaultIncomingMessageListener	A default implementation of a IncomingMessageListener.
DefaultResponseCallback	A default implementation of a ResponseCallback.
Discovery
FaultAwareResponseCallback
HTTPBinding	HTTP binding to allows access to DPWS devices and services.
HTTPSBinding	This Binding must be used for a secure service or a secure device.
ProtocolData
ProtocolInfo	Instances of this interface encapsulate information for a specific communication protocol, such as DPWS.

Exception Summary

ProtocolException	Exception which is thrown by protocol endpoints.
TimeoutException
VersionMismatchException	Thrown to indicate that an invalid version of a Web Services standard (such as SOAP, WS-Addresing, DPWS, etc.) was found within a DPWS message.

Package org.ws4d.java.communication Description

This package defines the communication protocol within the JMEDS framework.

A class is linked to a number of bindings, (implementing the Bindable interface), that is, one or more endpoints which allow access to a resource, a device or a service, for a specific type for messages and IncomingMessageListener. Each binding corresponds to a specific protocol or technology, uniquely identifiable via (CommunicationID). Further bindings can be added or removed by the client. A CommunicationManager handles connections manages resources. It must be called before any other method. Further methods register/unregister messageListeners for receiving incoming messages of the specified message type at the given binding address.

Each IncomingMessageHandler must be capable of handling the following types of events sent by the CommunicationManager:

• Hello and Bye messages
• Probe and Resolve messages (returning respectively a ProbeMatch and ResolveMatch message
• Subscribe, unsubscribe, and renew messages
• Get information messages

The ResponseCallback will in turn handle the output of the IncomingMessageHandler