Community
Participate
Working Groups
The ClientApplication and ServerApplication classes within the org.eclipse.ecf.provider.app package in the org.eclipse.ecf.provider both has main methods for a user to try running a ECF generic server or client. Both of them could originally be run without the OSGi framework, but this is no longer possible. This is because IDFactory and ContainerFactory now requires initialization work via the bundle activator classes, so they naturally fail (as the static instance retrieved is null).
Fixed with checkin on 10/20/2006. Now, the IDFactory and ContainerFactory both have a system property that they check: org.eclipse.ecf.core.identity.IDFactory.standalone and org.eclipse.ecf.core.ContainerFactory.standalone respectively. If this property is set to "true", then the extension point based setup for IDFactory and ContainerFactory are *skipped*, and the factories are assumed to be running standalone (i.e. for java applications). This means that it is then the responsibility of the application to see that the factories are populated with Namespace and ContainerTypeDescriptions as appropriate prior to calling one of the createID or createContainer methods (respectively). See the javadocs for the org.eclipse.ecf.core.identity.IDFactory and org.eclipse.ecf.core.ContainerFactory classes for more details.