This short guide explains the mechanics of taking applications written for Elvin3 and making them work with the new JE4 API for Elvin4. Some knowledge of the Elvin3 API for Elvin is assumed, but if you're new to Elvin in general, you may still find some useful information for developing clients. The good news is that JE4 is not that much different.
Developers report the change to the new API is anything but difficult.
Elvin4 provides a lot of new functionality over Elvin3, however, this document does not describe many of the new features. When Elvin3 was first released, the naming conventions of Java packages were still being established and DSTC used to release software under the dstc. It is now common for a fully qualified vendor domain to be used, and JE4 follows this convention. Rather than the dstc.elvin package, JE4 classes are located in the org.elvin.je4 package. There are other sub-packages within this package, but all of the essential API classes can be found in this single package.