As seen in [Fuchsia 101](Fuchsia-101), importers use import declaration as input. The information contained in the import declaration must be enough in order that the processor execute its role properly.
JAX-WS importer
-
JAX-WS service published
-
Interface(a') that represents the WSDL available in the OSGi platform that will import the service
-
jax-ws.importer.interfaces
-
className
-
endpoint.url
-
OSGi service registered with a' representing the JAX-WS (Remote service)
Detailed Description
Today to import the JAX-WS service Fushsia uses CXF. CXF is used in order to reduce the complexity in creating the connection and handling with different issues that may be raised.
MQTT importer
-
MQTT server with a known address
-
EventAdmin service configured in the machine that will receive MQTT event
-
id
-
mqtt.queue
-
A message will be published in EventAdmin in the queue mqtt.queue, meaning that it will use the same name as the MQTT queue
Detailed Description
MQTT is a protocol largely diffused for message exchange due to its good performance. The implementation used by Fuchsia to support MQTT was RabbitMQ
PubSubHubBub importer
PubSubHubBub, or simply PuSH, is a publish/subscribe protocol created by google and used by some of its tools.
-
PuSh server address
-
push.hub.url
-
push.hub.topic
-
push.subscriber.callback
-
push.eventAdmin.queue
-
A message will be published in EventAdmin in the queue $push.eventAdmin.queue, meaning that it will use the same name of queue as PuSH
Detailed Description
There are no well known and portable PuSH implementations, Fuchsia implemented partially PuSH specification