Re: Trying register an application via the registerJar command

[Susan Cline]

Many thanks, Dale.

Still trying to figure this out …

Cheers,

Susan
> On Sep 19, 2016, at 8:30 AM, Dale LaBossiere  wrote:
> 
> FYI I just created https://issues.apache.org/jira/browse/EDGENT-250 
>  to update IotProvider doc 
> related to registerJar().  You should consider adding commentary there as 
> part of your experiences — and/or consider tacking that jira and maybe even 
> enhancing the doc further in this space :-)
> 
> — Dale
> 
> 
>> On Sep 19, 2016, at 11:07 AM, Dale LaBossiere  wrote:
>> 
>> The TopologyBuilder.getBuilder() impl is bogus.  Looks like it’s copied from 
>> TestApplication().  All it does is return a builder (BiConsumer) that 
>> creates a topology consisting of a TStream containing one tuple with 
>> the app’s name and prints that stream.
>> 
>> Your getBuilder() impl needs to return a BiConsumer that builds your app’s 
>> topology.  Looks like that’s what your accept() is trying to do.  Seems like 
>> you want something like (though I’d rename that accept() to something like 
>> “buildTopology()” for clarity).
>> 
>>  public BiConsumer getBuilder() {
>>  return (t,c) -> accept(t,c);
>>  }   
>> 
>> Fix that and then see what happens regarding handling of the submit request. 
>>  You might also consider adding a println to your getBuilder() and accept() 
>> to verify they’re getting called.
>> 
>> — Dale
>> 
>>> On Sep 16, 2016, at 5:44 PM, Susan Cline  wrote:
>>> 
>>> Thanks Dale.  It did not work however, the results are the same after 
>>> removing the 3 lines before provider.start().
>>> When I submit the SpeedJarApp I can see this in the pi terminal (this is 
>>> the full output from when I started the registerJarExample application to 
>>> when I submitted the command):
>>> 
>>> pi@raspberrypi:~/devConf $ java -jar registerJarExample.jar 
>>> speed_sensor_config1.txt
>>> Sep 16, 2016 9:39:08 PM org.apache.edgent.runtime.appservice.AppService 
>>> registerTopology
>>> INFO: Register application name: edgentIotDevicePubSub
>>> Sep 16, 2016 9:39:08 PM org.apache.edgent.runtime.appservice.AppService 
>>> registerTopology
>>> INFO: Register application name: edgentIotCommandsToControl
>>> Sep 16, 2016 9:39:08 PM org.apache.edgent.runtime.appservice.AppService 
>>> registerTopology
>>> INFO: Register application name: edgentJobMonitorApp
>>> false
>>> Sep 16, 2016 9:39:09 PM pi.RegisterJarExample main
>>> INFO: Here is some info
>>> Sep 16, 2016 9:39:09 PM com.ibm.iotf.client.AbstractClient createClient
>>> INFO: pool-1-thread-22-edgentIotDevicePubSub: Org ID= ni6dcf
>>>   Client ID= d:ni6dcf:SpeedSensor:Pi3_SpeedSensor_1
>>> Sep 16, 2016 9:39:09 PM com.ibm.iotf.client.AbstractClient connect
>>> INFO: pool-1-thread-22-edgentIotDevicePubSub: Connecting client 
>>> d:ni6dcf:SpeedSensor:Pi3_SpeedSensor_1 to 
>>> ssl://ni6dcf.messaging.internetofthings.ibmcloud.com:8883 (attempt #1)...
>>> Sep 16, 2016 9:39:10 PM com.ibm.iotf.client.AbstractClient connect
>>> INFO: pool-1-thread-22-edgentIotDevicePubSub: Successfully connected to the 
>>> IBM Watson IoT Platform
>>> Sep 16, 2016 9:39:49 PM org.apache.edgent.runtime.appservice.AppService 
>>> registerJar
>>> INFO: Register jar: file:///home/pi/devConf/pi.sensors.jar
>>> Sep 16, 2016 9:39:49 PM org.apache.edgent.runtime.appservice.AppService 
>>> registerJar
>>> INFO: about to call registerTopology
>>> Sep 16, 2016 9:39:49 PM org.apache.edgent.runtime.appservice.AppService 
>>> registerTopology
>>> INFO: Register application name: SpeedJarApp
>>> SpeedJarApp
>>> Sep 16, 2016 9:40:11 PM org.apache.edgent.runtime.etiao.Executable$1 accept
>>> INFO: No more active user tasks
>>> 
>>> Thanks,
>>> 
>>> Susan
>>> 
>>> 
>>> 
 On Sep 16, 2016, at 10:32 AM, Dale LaBossiere  wrote:
 
 I haven’t digested the complete email message yet, but try removing those 
 three lines before provider.start() and try again.
 IotProvider already create/registers those services (described in its 
 javadoc).  I guess I wouldn’t be surprised if these extra additions might 
 much things up.
 
 — Dale
 
> On Sep 16, 2016, at 1:17 PM, Susan Cline  wrote:
> 
> I’ve gotten a step further, but I am still having problems.
> ...
> 
> public class RegisterJarExample {
>   IotProvider provider = new IotProvider(topology -> new 
> IotpDevice(topology, configFile));
>   /*
>* Not sure if I need the next few lines or not ...
>*/
>   JsonControlService control = new JsonControlService();
>   provider.getServices().addService(ControlService.class, 
> control); 
>   ApplicationService appService = 
> AppService.createAndRegister(provider, provider);
>   provider.start();
> 

[jira] [Comment Edited] (EDGENT-179) console: oplet coloring gradients "too close"

[Dale LaBossiere (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15504264#comment-15504264
 ] 

Dale LaBossiere edited comment on EDGENT-179 at 9/19/16 6:47 PM:
-

The general problem still seems to exist.
Since this jira was created, the console's handling Streamscope oplet was 
changed to make it like development provider injected metrics oplets - both 
small grey squares as see in your png.  So Streamscope won't ever be a problem 
:-)

When I try that "ParallelBalancedRecipe" sample now, it now shows the Peek and 
Union oplets as a blue color that's indistuinguishable to me.  In the png I'll 
attach, the blue oplets with the 22 and 25 in them (they're really oplets 11 
and 7 but that's a separate issue) are Peek oplets.  The blue oplet with the 26 
in it (really oplet 12) is a Union oplet.  And you can see in the oplet legend 
that they look to be the same color.

My fuzzy recollection was that the console code may not have been doing 
anything to avoid reusing a color or generating one that was "too close" to an 
already allocated one.


was (Author: dlaboss):
The general problem still seems to exist.
Since this jira was created, the console's handling Streamscope oplet was 
changed to make it like development provider injected metrics oplets - both 
small grey squares as see in your png.  So Streamscope won't ever be a problem 
:-)

When I try that "ParallelBalancedRecipe" sample now, it now shows the Peek and 
Union oplets as a blue color that's indistuinguishable to me.  In the png I'll 
attach, the blue oplets with the 22 and 25 in them (they're really oplets 11 
and 7 but that's a separate issue) are Peek oplets.  The blue oplet with the 26 
in it (really oplet 12) is a Union oplet.  And you can see in the oplet legend 
that they look to be the same color.

> console: oplet coloring gradients "too close"
> -
>
> Key: EDGENT-179
> URL: https://issues.apache.org/jira/browse/EDGENT-179
> Project: Edgent
>  Issue Type: Bug
>  Components: Console
>Reporter: Dale LaBossiere
>Priority: Minor
> Attachments: EDGENT-179_oplet_colors.png, Screen Shot 2016-09-19 at 
> 2.22.00 PM.png
>
>
> The oplet color generator ends up yielding two light purple-ish colors for 
> two different kinds of (adjacent) oplets and one can't tell them apart.  One 
> is a Sink the other is a subtype of Peek - a StreamScope.
> I was seeing this in a ParallelBalancedRecipe app of mine.  I can provide it 
> if really necessary to repro/improve this.



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

[jira] [Commented] (EDGENT-179) console: oplet coloring gradients "too close"

[Dale LaBossiere (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15504264#comment-15504264
 ] 

Dale LaBossiere commented on EDGENT-179:


The general problem still seems to exist.
Since this jira was created, the console's handling Streamscope oplet was 
changed to make it like development provider injected metrics oplets - both 
small grey squares as see in your png.  So Streamscope won't ever be a problem 
:-)

When I try that "ParallelBalancedRecipe" sample now, it now shows the Peek and 
Union oplets as a blue color that's indistuinguishable to me.  In the png I'll 
attach, the blue oplets with the 22 and 25 in them (they're really oplets 11 
and 7 but that's a separate issue) are Peek oplets.  The blue oplet with the 26 
in it (really oplet 12) is a Union oplet.  And you can see in the oplet legend 
that they look to be the same color.

> console: oplet coloring gradients "too close"
> -
>
> Key: EDGENT-179
> URL: https://issues.apache.org/jira/browse/EDGENT-179
> Project: Edgent
>  Issue Type: Bug
>  Components: Console
>Reporter: Dale LaBossiere
>Priority: Minor
> Attachments: EDGENT-179_oplet_colors.png, Screen Shot 2016-09-19 at 
> 2.22.00 PM.png
>
>
> The oplet color generator ends up yielding two light purple-ish colors for 
> two different kinds of (adjacent) oplets and one can't tell them apart.  One 
> is a Sink the other is a subtype of Peek - a StreamScope.
> I was seeing this in a ParallelBalancedRecipe app of mine.  I can provide it 
> if really necessary to repro/improve this.



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

[jira] [Updated] (EDGENT-179) console: oplet coloring gradients "too close"

[Queenie Ma (JIRA)]

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

Queenie Ma updated EDGENT-179:
--
Attachment: EDGENT-179_oplet_colors.png

> console: oplet coloring gradients "too close"
> -
>
> Key: EDGENT-179
> URL: https://issues.apache.org/jira/browse/EDGENT-179
> Project: Edgent
>  Issue Type: Bug
>  Components: Console
>Reporter: Dale LaBossiere
>Priority: Minor
> Attachments: EDGENT-179_oplet_colors.png
>
>
> The oplet color generator ends up yielding two light purple-ish colors for 
> two different kinds of (adjacent) oplets and one can't tell them apart.  One 
> is a Sink the other is a subtype of Peek - a StreamScope.
> I was seeing this in a ParallelBalancedRecipe app of mine.  I can provide it 
> if really necessary to repro/improve this.



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

[jira] [Commented] (EDGENT-179) console: oplet coloring gradients "too close"

[Queenie Ma (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15504099#comment-15504099
 ] 

Queenie Ma commented on EDGENT-179:
---

It looks like this may have been fixed in [PR 
#116|https://github.com/apache/incubator-edgent/pull/116/commits/18c2480560544aa56cb904e0e5f351fbf956fcb7]
 as the colors are not too similar anymore.  StreamScope oplets are 
{color:#c7c7c7}#c7c7c7{color} (light grey), and Sink oplets are 
{color:#c5b0d5}#c5b0d5{color} (light purple). See screenshot.

[~dlaboss], is this okay to close?

> console: oplet coloring gradients "too close"
> -
>
> Key: EDGENT-179
> URL: https://issues.apache.org/jira/browse/EDGENT-179
> Project: Edgent
>  Issue Type: Bug
>  Components: Console
>Reporter: Dale LaBossiere
>Priority: Minor
> Attachments: EDGENT-179_oplet_colors.png
>
>
> The oplet color generator ends up yielding two light purple-ish colors for 
> two different kinds of (adjacent) oplets and one can't tell them apart.  One 
> is a Sink the other is a subtype of Peek - a StreamScope.
> I was seeing this in a ParallelBalancedRecipe app of mine.  I can provide it 
> if really necessary to repro/improve this.



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

[jira] [Closed] (EDGENT-245) replace the favicon.png for the console with a new one that uses E instead of Q

[Queenie Ma (JIRA)]

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

Queenie Ma closed EDGENT-245.
-
Resolution: Resolved

> replace the favicon.png for the console with a new one that uses E instead of 
> Q
> ---
>
> Key: EDGENT-245
> URL: https://issues.apache.org/jira/browse/EDGENT-245
> Project: Edgent
>  Issue Type: Task
>  Components: Console
>Reporter: Susan L. Cline
>Assignee: Queenie Ma
>Priority: Minor
>  Labels: newbie
>
> The old favicon.png has a 'Q' in the middle of it.  It needs to have the 'E' 
> in the middle of it now that the project has changed from 'Quarks' to 
> 'Edgent'.  This would be a great newbie item.



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

[jira] [Commented] (EDGENT-245) replace the favicon.png for the console with a new one that uses E instead of Q

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15503838#comment-15503838
 ] 

ASF GitHub Bot commented on EDGENT-245:
---

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-edgent/pull/192


> replace the favicon.png for the console with a new one that uses E instead of 
> Q
> ---
>
> Key: EDGENT-245
> URL: https://issues.apache.org/jira/browse/EDGENT-245
> Project: Edgent
>  Issue Type: Task
>  Components: Console
>Reporter: Susan L. Cline
>Assignee: Queenie Ma
>Priority: Minor
>  Labels: newbie
>
> The old favicon.png has a 'Q' in the middle of it.  It needs to have the 'E' 
> in the middle of it now that the project has changed from 'Quarks' to 
> 'Edgent'.  This would be a great newbie item.



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

[GitHub] incubator-edgent pull request #192: [EDGENT-245] Console: Update Apache Edge...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-edgent/pull/192


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Trying register an application via the registerJar command

[Dale LaBossiere]

FYI I just created https://issues.apache.org/jira/browse/EDGENT-250 
 to update IotProvider doc 
related to registerJar().  You should consider adding commentary there as part 
of your experiences — and/or consider tacking that jira and maybe even 
enhancing the doc further in this space :-)

— Dale


> On Sep 19, 2016, at 11:07 AM, Dale LaBossiere  wrote:
> 
> The TopologyBuilder.getBuilder() impl is bogus.  Looks like it’s copied from 
> TestApplication().  All it does is return a builder (BiConsumer) that creates 
> a topology consisting of a TStream containing one tuple with the 
> app’s name and prints that stream.
> 
> Your getBuilder() impl needs to return a BiConsumer that builds your app’s 
> topology.  Looks like that’s what your accept() is trying to do.  Seems like 
> you want something like (though I’d rename that accept() to something like 
> “buildTopology()” for clarity).
> 
>   public BiConsumer getBuilder() {
>   return (t,c) -> accept(t,c);
>   }   
> 
> Fix that and then see what happens regarding handling of the submit request.  
> You might also consider adding a println to your getBuilder() and accept() to 
> verify they’re getting called.
> 
> — Dale
> 
>> On Sep 16, 2016, at 5:44 PM, Susan Cline  wrote:
>> 
>> Thanks Dale.  It did not work however, the results are the same after 
>> removing the 3 lines before provider.start().
>> When I submit the SpeedJarApp I can see this in the pi terminal (this is the 
>> full output from when I started the registerJarExample application to when I 
>> submitted the command):
>> 
>> pi@raspberrypi:~/devConf $ java -jar registerJarExample.jar 
>> speed_sensor_config1.txt
>> Sep 16, 2016 9:39:08 PM org.apache.edgent.runtime.appservice.AppService 
>> registerTopology
>> INFO: Register application name: edgentIotDevicePubSub
>> Sep 16, 2016 9:39:08 PM org.apache.edgent.runtime.appservice.AppService 
>> registerTopology
>> INFO: Register application name: edgentIotCommandsToControl
>> Sep 16, 2016 9:39:08 PM org.apache.edgent.runtime.appservice.AppService 
>> registerTopology
>> INFO: Register application name: edgentJobMonitorApp
>> false
>> Sep 16, 2016 9:39:09 PM pi.RegisterJarExample main
>> INFO: Here is some info
>> Sep 16, 2016 9:39:09 PM com.ibm.iotf.client.AbstractClient createClient
>> INFO: pool-1-thread-22-edgentIotDevicePubSub: Org ID= ni6dcf
>>Client ID= d:ni6dcf:SpeedSensor:Pi3_SpeedSensor_1
>> Sep 16, 2016 9:39:09 PM com.ibm.iotf.client.AbstractClient connect
>> INFO: pool-1-thread-22-edgentIotDevicePubSub: Connecting client 
>> d:ni6dcf:SpeedSensor:Pi3_SpeedSensor_1 to 
>> ssl://ni6dcf.messaging.internetofthings.ibmcloud.com:8883 (attempt #1)...
>> Sep 16, 2016 9:39:10 PM com.ibm.iotf.client.AbstractClient connect
>> INFO: pool-1-thread-22-edgentIotDevicePubSub: Successfully connected to the 
>> IBM Watson IoT Platform
>> Sep 16, 2016 9:39:49 PM org.apache.edgent.runtime.appservice.AppService 
>> registerJar
>> INFO: Register jar: file:///home/pi/devConf/pi.sensors.jar
>> Sep 16, 2016 9:39:49 PM org.apache.edgent.runtime.appservice.AppService 
>> registerJar
>> INFO: about to call registerTopology
>> Sep 16, 2016 9:39:49 PM org.apache.edgent.runtime.appservice.AppService 
>> registerTopology
>> INFO: Register application name: SpeedJarApp
>> SpeedJarApp
>> Sep 16, 2016 9:40:11 PM org.apache.edgent.runtime.etiao.Executable$1 accept
>> INFO: No more active user tasks
>> 
>> Thanks,
>> 
>> Susan
>> 
>> 
>> 
>>> On Sep 16, 2016, at 10:32 AM, Dale LaBossiere  wrote:
>>> 
>>> I haven’t digested the complete email message yet, but try removing those 
>>> three lines before provider.start() and try again.
>>> IotProvider already create/registers those services (described in its 
>>> javadoc).  I guess I wouldn’t be surprised if these extra additions might 
>>> much things up.
>>> 
>>> — Dale
>>> 
 On Sep 16, 2016, at 1:17 PM, Susan Cline  wrote:
 
 I’ve gotten a step further, but I am still having problems.
 ...
 
 public class RegisterJarExample {
IotProvider provider = new IotProvider(topology -> new 
 IotpDevice(topology, configFile));
/*
 * Not sure if I need the next few lines or not ...
 */
JsonControlService control = new JsonControlService();
provider.getServices().addService(ControlService.class, 
 control); 
ApplicationService appService = 
 AppService.createAndRegister(provider, provider);
provider.start();

logger.info("Here is some info");
}

 }
>>> 
>> 
> 

[jira] [Created] (EDGENT-250) update IotProvider control service commands doc

[Dale LaBossiere (JIRA)]

Dale LaBossiere created EDGENT-250:
--

 Summary: update IotProvider control service commands doc
 Key: EDGENT-250
 URL: https://issues.apache.org/jira/browse/EDGENT-250
 Project: Edgent
  Issue Type: Task
  Components: API
Reporter: Dale LaBossiere


providers.iot.package-info.java lacks the important 
ApplicationServiceMXBean.registerJar() operation.

At a higher level, the info in package-info was too hard for me to find.  
Suggest either migrating it into IotProvider.java or adding a prominent mention 
and link to it there.  

Also feels like ApplicationServiceMxBean,JobMxBean, and/or JsonControlService 
should somehow lead the reader in that direction.



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

Re: Trying register an application via the registerJar command

[Dale LaBossiere]

The TopologyBuilder.getBuilder() impl is bogus.  Looks like it’s copied from 
TestApplication().  All it does is return a builder (BiConsumer) that creates a 
topology consisting of a TStream containing one tuple with the app’s 
name and prints that stream.

Your getBuilder() impl needs to return a BiConsumer that builds your app’s 
topology.  Looks like that’s what your accept() is trying to do.  Seems like 
you want something like (though I’d rename that accept() to something like 
“buildTopology()” for clarity).

   public BiConsumer getBuilder() {
return (t,c) -> accept(t,c);
   }   

Fix that and then see what happens regarding handling of the submit request.  
You might also consider adding a println to your getBuilder() and accept() to 
verify they’re getting called.

— Dale

> On Sep 16, 2016, at 5:44 PM, Susan Cline  wrote:
> 
> Thanks Dale.  It did not work however, the results are the same after 
> removing the 3 lines before provider.start().
> When I submit the SpeedJarApp I can see this in the pi terminal (this is the 
> full output from when I started the registerJarExample application to when I 
> submitted the command):
> 
> pi@raspberrypi:~/devConf $ java -jar registerJarExample.jar 
> speed_sensor_config1.txt
> Sep 16, 2016 9:39:08 PM org.apache.edgent.runtime.appservice.AppService 
> registerTopology
> INFO: Register application name: edgentIotDevicePubSub
> Sep 16, 2016 9:39:08 PM org.apache.edgent.runtime.appservice.AppService 
> registerTopology
> INFO: Register application name: edgentIotCommandsToControl
> Sep 16, 2016 9:39:08 PM org.apache.edgent.runtime.appservice.AppService 
> registerTopology
> INFO: Register application name: edgentJobMonitorApp
> false
> Sep 16, 2016 9:39:09 PM pi.RegisterJarExample main
> INFO: Here is some info
> Sep 16, 2016 9:39:09 PM com.ibm.iotf.client.AbstractClient createClient
> INFO: pool-1-thread-22-edgentIotDevicePubSub: Org ID= ni6dcf
> Client ID= d:ni6dcf:SpeedSensor:Pi3_SpeedSensor_1
> Sep 16, 2016 9:39:09 PM com.ibm.iotf.client.AbstractClient connect
> INFO: pool-1-thread-22-edgentIotDevicePubSub: Connecting client 
> d:ni6dcf:SpeedSensor:Pi3_SpeedSensor_1 to 
> ssl://ni6dcf.messaging.internetofthings.ibmcloud.com:8883 (attempt #1)...
> Sep 16, 2016 9:39:10 PM com.ibm.iotf.client.AbstractClient connect
> INFO: pool-1-thread-22-edgentIotDevicePubSub: Successfully connected to the 
> IBM Watson IoT Platform
> Sep 16, 2016 9:39:49 PM org.apache.edgent.runtime.appservice.AppService 
> registerJar
> INFO: Register jar: file:///home/pi/devConf/pi.sensors.jar
> Sep 16, 2016 9:39:49 PM org.apache.edgent.runtime.appservice.AppService 
> registerJar
> INFO: about to call registerTopology
> Sep 16, 2016 9:39:49 PM org.apache.edgent.runtime.appservice.AppService 
> registerTopology
> INFO: Register application name: SpeedJarApp
> SpeedJarApp
> Sep 16, 2016 9:40:11 PM org.apache.edgent.runtime.etiao.Executable$1 accept
> INFO: No more active user tasks
> 
> Thanks,
> 
> Susan
> 
> 
> 
>> On Sep 16, 2016, at 10:32 AM, Dale LaBossiere  wrote:
>> 
>> I haven’t digested the complete email message yet, but try removing those 
>> three lines before provider.start() and try again.
>> IotProvider already create/registers those services (described in its 
>> javadoc).  I guess I wouldn’t be surprised if these extra additions might 
>> much things up.
>> 
>> — Dale
>> 
>>> On Sep 16, 2016, at 1:17 PM, Susan Cline  wrote:
>>> 
>>> I’ve gotten a step further, but I am still having problems.
>>> ...
>>> 
>>> public class RegisterJarExample {
>>> IotProvider provider = new IotProvider(topology -> new 
>>> IotpDevice(topology, configFile));
>>> /*
>>>  * Not sure if I need the next few lines or not ...
>>>  */
>>> JsonControlService control = new JsonControlService();
>>> provider.getServices().addService(ControlService.class, 
>>> control); 
>>> ApplicationService appService = 
>>> AppService.createAndRegister(provider, provider);
>>> provider.start();
>>> 
>>> logger.info("Here is some info");
>>> }
>>> 
>>> }
>> 
> 

[GitHub] incubator-edgent pull request #190: Edgent-240 [gradle] Overhaul dependency ...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-edgent/pull/190


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---