edgent-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dale LaBossiere (JIRA)" <j...@apache.org>
Subject [jira] [Created] (EDGENT-363) clarify / disallow null topology names
Date Thu, 05 Jan 2017 22:07:58 GMT
Dale LaBossiere created EDGENT-363:

             Summary: 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

View raw message