eclipse - Starting OSGI Declarative Services causing thread error -


I have a RCP 3.7 application in which two database connection is required, the code for each database is in a separate bundle first From the startup startup, Activator.start () was done in the way. I have re-enforced the code heavily to transfer the database to two declaratory services. This gave the purpose of breaking the stringent coupling and breaking the highly exposed package exposure (almost everything was exported) in the bundles.

The challenge is now that both of the services do not start very quickly, the workload load and the thread are being violated. I have both services immediately = true. OPG) is on-1 (default), Equinox.ede and Equinoxamem2, the core. By default on time. I have tried to add the initial level for my bundles, but it did not help in getting them removed.

Any ideas or suggestions about starting a database before service return?

It seems that you are reaching SWT from within the DS activation thread. Please use Display.asyncExec to access SWT code from another thread. To access the exhibit see PlatformUI.getWorkbench.


Comments

Popular posts from this blog

Member with no value in F# -

java - Joda Time Interval Not returning what I expect -

c# - Showing a SelectedItem's Property -