rogierc / mule-coap-server-connector

The CoapServer Connector adds CoAP server capability to Mule Enterprise Service Bus. With it Mule applications can implement services that can be accessed by clients using the CoAP protocol.

Project has moved to: https://github.com/teslanet-nl/mule-coap-server-connector

Mule CoAP connector - CoapServer

Mule CoAP connector is an Anypoint Connector implementation of the RFC7252 - Constrained Application Protocol. With it Mule applications become CoAP capable and can communicate with other CoAP capable devices and services, realising Internet of Things solutions (IoT).

The connector uses Californium, a Java CoAP implementation. More information about Californium and CoAP can be found at:

• http://www.eclipse.org/californium/
• http://coap.technology/.

This component - the CoapServer Connector - is one of three parts of the Mule CoAP package.
The other two being the CoapClient Connector and the Mule CoAP Commons component .

The CoapServer Connector adds CoAP server capability to Mule enterprise service bus. With it Mule applications can implement services that can be accessed by clients using the CoAP protocol.

The complete Mule CoAP Connector documentation can be found on Teslanet.nl

Mule supported versions

• Mule 3.8.x
• Mule 3.9.x

CoAP supported versions

IETF rfc7252

Dependencies

• Californium 1.0.6
• Mule Coap Commons 1.0.0

Installation

For beta connectors you can download the source code and build it in Anypoint Studio:

• Import source into Anypoint Studio
• Select the imported project
• Build and install: Context Menu -> Anypoint Connector / Install or Update

Usage

See the Userguide on Teslanet.nl

Using in Maven Projects

Mule CoAP artefact releases will be published to Maven Central. The CloapServer connector can be used in your project by adding following dependency to your pom.xml (without the dots):

  <dependencies>
    ...
    <dependency>
            <groupId>nl.teslanet.mule.transport.coap</groupId>
            <artifactId>mule-coap-server-connector</artifactId>
            <version>1.0.0</version>
    </dependency>
    ...
  </dependencies>
  ...

Reporting Issues

We use GitHub:Issues for tracking issues with this connector. You can report new issues at this link https://github.com/rogierc/mule-coap-server-connector/issues.

Contact

A bug, an idea, an issue? Create an issue on https://github.com/rogierc/mule-coap-server-connector/issues

Contributing

Use issues or pull-requests on your fork.

mule-coap-server-connector's Issues

NullMessage should result in empty response

the response handling calls toString when payload is not a Byte[], which doesn't result in a emtpy string on a NullMassage. Add specific handling on a NullMessage response.