Package org.somda.sdc.dpws.device.helper

Class ByteResourceHandler

java.lang.Object

org.somda.sdc.dpws.device.helper.ByteResourceHandler

All Implemented Interfaces:

HttpHandler

public class ByteResourceHandler
extends Object
implements HttpHandler

HTTP handler that facilitates responding with arbitrary byte sequences.

Constructor Summary

Constructors

Constructor	Description
ByteResourceHandler(byte[] resourceBytes)	Constructor.

Method Summary

Modifier and Type	Method	Description
void	handle(InputStream inStream, OutputStream outStream, CommunicationContext communicationContext)	Callback that is invoked by HttpServerRegistry whenever a respective context path is matched.

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Details

ByteResourceHandler

public ByteResourceHandler(byte[] resourceBytes)

Constructor.

Parameters:

resourceBytes - the bytes that are supposed to be returned on any incoming network request.

Method Details

handle

public void handle(InputStream inStream,
 OutputStream outStream,
 CommunicationContext communicationContext)
            throws HttpException

Description copied from interface: HttpHandler

Callback that is invoked by HttpServerRegistry whenever a respective context path is matched.

Specified by:

handle in interface HttpHandler

Parameters:

inStream - stream of the incoming SOAP request. The caller is responsible for closing the stream.

outStream - stream of the outgoing SOAP response. The caller is responsible for closing the stream.

communicationContext - information from the transport and application layer, e.g., local address, local port, certificate data etc.

Throws:

HttpException - if there is a SOAP fault thrown that is supposed to cause the HTTP layer to attach a status code other than 200. If the exception includes a message, then the caller is supposed to put the text to the HTTP response. If the exception does not include a message (length is 0), then the caller is supposed to put the outStream content to the HTTP response.