You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@edgent.apache.org by "Dale LaBossiere (JIRA)" <ji...@apache.org> on 2017/01/10 20:23:58 UTC

[jira] [Resolved] (EDGENT-363) clarify / disallow null topology names

     [ https://issues.apache.org/jira/browse/EDGENT-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dale LaBossiere resolved EDGENT-363.
------------------------------------
    Resolution: Fixed

resolved via https://github.com/apache/incubator-edgent/pull/271

> clarify / disallow null topology names
> --------------------------------------
>
>                 Key: EDGENT-363
>                 URL: https://issues.apache.org/jira/browse/EDGENT-363
>             Project: Edgent
>          Issue Type: Bug
>          Components: API
>            Reporter: Dale LaBossiere
>            Assignee: Dale LaBossiere
>
> TopologyProvider.newTopology(String name) doesn't state that null/empty names are disallowed.  DirectProvider allows them.  But other places in the code will be unhappy or non-sensical if they are - e.g., Etaio's synthesis of a job-name.
> ApplicationService.registerTopology() and IotProvider.registerTopology() are other places.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)