Jump to: navigation, search

ECF Pitfalls

Revision as of 15:00, 27 January 2009 by F.hackenberger.chello.at (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Shared Object API

  • Make sure you export the package containing the shared object classes. Otherwise the clients will never receive the replica objects. There is no error message if you forget about that.
  • You need to add at least (not sure if all of them are required, please correct) the following plugins as dependencies to get the shared object api with the ECF generic container working:
    • org.eclipse.ecf
    • org.eclipse.ecf.sharedobject
    • org.eclipse.ecf.datashare
    • org.eclipse.ecf.provider
    • org.eclipse.ecf.provider.datashare
  • If you don't receive an object on your clients which you have just added on your master client, make sure that all objects which have to go over the wire are actually serialisable. You can easily spot offending classes, by stopping in the debugger right before the call to soManager.addSharedObject(...), enabling a breakpoint on the NotSerializableException and stepping over the addSharedObject() call.