Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 86ADC200C15 for ; Wed, 8 Feb 2017 17:28:45 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 85397160B5A; Wed, 8 Feb 2017 16:28:45 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id D2BEA160B49 for ; Wed, 8 Feb 2017 17:28:44 +0100 (CET) Received: (qmail 89593 invoked by uid 500); 8 Feb 2017 16:28:44 -0000 Mailing-List: contact dev-help@edgent.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@edgent.apache.org Delivered-To: mailing list dev@edgent.apache.org Received: (qmail 89581 invoked by uid 99); 8 Feb 2017 16:28:44 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Feb 2017 16:28:44 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 83523C24A7 for ; Wed, 8 Feb 2017 16:28:43 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.199 X-Spam-Level: X-Spam-Status: No, score=-1.199 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id e-UXUoIIfgbu for ; Wed, 8 Feb 2017 16:28:42 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id A24B261004 for ; Wed, 8 Feb 2017 16:28:42 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 0D240E031F for ; Wed, 8 Feb 2017 16:28:42 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id B733124D30 for ; Wed, 8 Feb 2017 16:28:41 +0000 (UTC) Date: Wed, 8 Feb 2017 16:28:41 +0000 (UTC) From: "Dale LaBossiere (JIRA)" To: dev@edgent.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (EDGENT-376) Support an edge device using both the Edgent API and WIoTP "Managed Device" APIs MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 08 Feb 2017 16:28:45 -0000 [ https://issues.apache.org/jira/browse/EDGENT-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere resolved EDGENT-376. ------------------------------------ Resolution: Fixed resolved via https://github.com/apache/incubator-edgent/pull/282 > Support an edge device using both the Edgent API and WIoTP "Managed Device" APIs > -------------------------------------------------------------------------------- > > Key: EDGENT-376 > URL: https://issues.apache.org/jira/browse/EDGENT-376 > Project: Edgent > Issue Type: Improvement > Components: Connectors > Reporter: Dale LaBossiere > Assignee: Dale LaBossiere > > Use case: I need to be able to write an edge device application that uses both the Edgent APIs/programming model for analytics and the IBM Watson IoT Platform "Managed Device" APIs for other capabilities (e.g., to support the WIoTP "reboot the device" protocol). > I don't need the Edgent IoT connector to support WIoTP defined "Managed Device" capabilities -- e.g., I don't need my Edgent application to be able to create a TStream of subscribed "WIoTP device management" commands using {{IotDevice.commands(...)}}. > Today the [IotpDevice|https://github.com/apache/incubator-edgent/blob/master/connectors/iotp/src/main/java/org/apache/edgent/connectors/iotp/IotpDevice.java] connector precludes this use case. It hides the WIoTP API objects used to connect to WIoTP. The WIoTP {{DeviceClient}} API is for a simple device (used by today's connector); {{ManagedDevice}} is for a "managed device" -- {{ManagedDevice extends DeviceClient}}. > I think the best way to enable this use case, and generally add more flexibility in configuring an underlying WIoTP connection, would be to add a {{IotpDevice(DeviceClient)}} constructor, allowing the application to create and use the ManagedDevice object for WIoTP managed device capabilities and intialize the IotpDevice connector with it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)