Hi All, Current structure for device type plugin for WSO2 IoT looks like following:
devicetype-plugin | - device manager extension (An OSGi service ) | - api (jax-rs) | - UI | - analytics (descriptors - deployer) However, what goes inside device manager extension component is pretty much a boiler plate code that can be replaced by a descriptor. This is common for all the plugins (eg: Android, Windows, Virtual Firalarm, Raspberypi, Android Sense ...) we have written so far. But the ability to write Java based device manager extension can be useful @ times where custom behaviour is needed. So I have done a PoC that will allow both of these approaches to be supported when writing a device type plugin. This concept is previously discussed in [1] too. A sample descriptor is in [2]. [1] [Architecture] [CDM-F] "Descriptor"-driven plug-ins for CDM-F [2] https://github.com/ayyoob/carbon-device-mgt/blob/deploye r/components/device-mgt-extensions/org.wso2.carbon.device.mg t.extensions.device.type.deployer/src/test/resources/sample.xml [3] https://github.com/ayyoob/carbon-device-mgt/tree/deploye r/components/device-mgt-extensions/org.wso2.carbon.device.mg t.extensions.device.type.deployer Thanks, *Ayyoob Hamza* *Software Engineer* WSO2 Inc.; http://wso2.com email: ayy...@wso2.com cell: +94 77 1681010 <%2B94%2077%207779495>
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
