documents/embedding/embjava.tex

67 QuickTest.java} works. In the other sections of the document you will
221 There are a number of classes which implement these interfaces. In the case
224 classes varies from class to class. In the case of {\it EmbeddedEclipse}
233 interface} or {\it EclipseEngine} \index{EclipseEngine interface}. In the
239 In order to clean up, after the Java program has finished interacting
243 interfaces.  In the case of {\tt QuickTest.java}, termination is done
337 In this example we use an {\it CompoundTermImpl} constructor whose
466 \ref{sec:ji-atoms-and-terms}). In this case the term becomes the
509 In the returned {\it CompoundTerm} instantiated variables are replaced
620 In the Java-{\eclipse} Interface, {\it queues} are one-way data
641 feature is discussed in Section \ref{sec:ji-queue-listeners}. In some
739 reading and writing whole terms. In the underlying implementation of these
777 EXDR format. In other words, we usually wrap these classes around {\it
1102 peer connection. In particular, those related to the opening and closing of
1131 In the first case you can either specify system properties (by passing
1153 respectively. In each case the option is an integer representing the
1259 embedded {\eclipse} engine. In other words, by invoking {\tt destroy},
1323 In some applications, for example where Java is used to visualise
1425 In both connection sequences, the peer name indexing the connection is
1444 invoking the {\tt resume()} method on a {\it RemoteEclipse}\index{RemoteEclipse class}. In this
1453 builtin. In this case the Java thread which passed execution to
1458 an execution of a \bipref{remote_yield/1}{../bips/kernel/externals/remote_yield-1.html} goal in most cases. In addition,