On 11/19/2016 6:16 PM, Jay Jay Billings
wrote:
Scott,
I got the AbstractExecutor error to go away by creating a
new workspace. That's not ideal, but it is simple enough
with ICE's dev menu.
Ok I've resolved the bug [1].
I was able to get the perspective running. Screenshot
attached. It looks like it is showing the local instance of
ICE exporting the remote service.
I would like to try to connect to another instance of ice
using the endpoint description you mentioned. Do you have the
format for the file documented somewhere?
Yes, the EDEF format (endpoint description extender format) is
defined by the Remote Service Admin specification...chap 122 in the
enterprise spec.
We also have ECF documentation on using EDEF to do consumer-side
discovery of remote services [2]. ECF's implementation also
provides EndpointDescriptionReader and EndpointDescriptionWriter
classes that implement reading/writing the EDEF format.
For context: there are multiple ways for consumers to discover and
import remote services. It's possible (via spec) to read and
automatically import remote services by embedding edef files in a
bundle [2]). It's possible to manually read in an edef xml file,
modify necessary properties, and explicitly import the resulting
EDEF, and it's also possible to use one of several network discovery
providers (zookeeper, etcd, zeroconf, slp, dnssd, others) to publish
and discover remote services via the network. I mention these
because the use cases for remote service discovery are pretty
varied.
And as I mentioned in a previous note, the new Eclipse Remote
Service perspective also has an EndpointDescription view that allows
EDEF files to be interactively read from the file system and
imported. This is mostly intended to aid the testing and debugging
of remote services.
In any event, EDEF is probably what you want to start, and ECF's
impl fully supports the spec and provides support for
reading/writing. If you want other/more information please let me
know and I'll be happy to provide it.
BTW, I loaded the neon.target for ICE on the given branc and am
getting a large number of error messages about the maven build as
per below. Any idea what's going wrong there? I would like to try
out ICE, and I may be able to help with the remote services
development, testing and debugging.
Thanks,
Scott
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=507717
[2]
http://wiki.eclipse.org/EIG:File-based_Discovery_with_the_Endpoint_Description_Extender_Format
Errors in ICE workspace (sample):
Description Resource Path Location Type
Plugin execution not covered by lifecycle configuration:
org.apache.maven.plugins:maven-clean-plugin:2.5:clean (execution:
default-clean-1, phase: initialize) pom.xml
/org.eclipse.ice.product line 15 Maven Project Build Lifecycle
Mapping Problem
Plugin execution not covered by lifecycle configuration:
org.apache.maven.plugins:maven-clean-plugin:2.5:clean (execution:
default-clean-1, phase: initialize) pom.xml
/org.eclipse.ice.repository line 15 Maven Project Build
Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration:
org.eclipse.tycho:tycho-compiler-plugin:0.24.0:compile (execution:
default-compile, phase: compile) pom.xml
/org.eclipse.ice.caebat.batml line 15 Maven Project Build
Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration:
org.eclipse.tycho:tycho-compiler-plugin:0.24.0:compile (execution:
default-compile, phase: compile) pom.xml
/org.eclipse.ice.caebat.batml.test line 14 Maven Project Build
Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration:
org.eclipse.tycho:tycho-compiler-plugin:0.24.0:compile (execution:
default-compile, phase: compile) pom.xml
/org.eclipse.ice.client line 14 Maven Project Build Lifecycle
Mapping Problem
|