Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
ECF Pitfalls
Revision as of 14:57, 27 January 2009 by F.hackenberger.chello.at (Talk | contribs) (→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 the replica shared objects you have just added on other clients, make sure that all objects which have to go over the wire are actually serialisable. You can easily spot offending classed, by stopping in the debugger right before the call to soManager.addSharedObject(...), enabling a breakpoint on the NotSerializableException and stepping over the addSharedObject() call.