Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ecf-dev] Remote service registration and discovery in an eclipse product

Hi Scott,

Bundles seem to be okay. Distribution seems to work, just the discovery doesn't. Hm, it's also not a Windows problem, the same with Linux.

Framework is launched.

id    State       Bundle
0    ACTIVE      org.eclipse.osgi_3.6.1.R36x_v20100806
1    ACTIVE      org.eclipse.equinox.registry_3.5.0.v20100503
2    ACTIVE      org.eclipse.ecf.discovery_4.0.0.v20101029-1626
3    ACTIVE      devsosgi.rootsimulator.analytical_1.0.0.qualifier
4    ACTIVE      org.eclipse.core.contenttype_3.4.100.v20100505-1235
5    ACTIVE      org.eclipse.ecf_3.1.0.v20100529-0735
6    ACTIVE      org.eclipse.equinox.concurrent_1.0.100.v20100503
7    ACTIVE      org.eclipse.core.jobs_3.5.1.R36x_v20100824
8 ACTIVE org.eclipse.ecf.osgi.services.discovery_1.2.0.v20101029-1626
9    ACTIVE      org.eclipse.osgi.services_3.2.100.v20100503
10    ACTIVE      org.objectweb.asm_3.2.0.v200909071300
11    ACTIVE      de.ooflex.misc_1.0.0.qualifier
12    ACTIVE      org.eclipse.osgi.util_3.2.100.v20100503
13    ACTIVE      devsosgi.rootsimulator.rt_1.0.0.qualifier
14    ACTIVE      devsosgi.controller_1.0.0
15    ACTIVE      devsosgi.simulator.atomic_1.0.0.qualifier
16    ACTIVE      org.eclipse.ecf.remoteservice_5.0.0.v20101029-1626
17    ACTIVE      devsosgi.simulator.coupled_1.0.0.qualifier
18    ACTIVE      org.eclipse.ecf.provider.jmdns_4.1.0.v20101029-1626
19    ACTIVE      org.eclipse.ecf.osgi.services.distribution_1.3.0.qualifier
20    ACTIVE      org.eclipse.equinox.common_3.6.0.v20100503
21    ACTIVE      org.eclipse.ecf.provider.r_osgi_3.1.0.qualifier
22    RESOLVED    devsosgi.log4jproperties_1.0.0.qualifier
                Master=23
23    ACTIVE      org.apache.log4j_1.2.15.v201005080500
                Fragments=22
24    ACTIVE      org.eclipse.ecf.identity_3.1.0.v20100529-0735
25    ACTIVE      org.eclipse.core.runtime_3.6.0.v20100505
26    ACTIVE      org.eclipse.equinox.preferences_3.3.0.v20100503
27    ACTIVE      org.eclipse.ecf.provider_4.0.0.qualifier
28    ACTIVE      ch.ethz.iks.r_osgi.remote_1.0.0.RC4_qualifier
29    ACTIVE      org.eclipse.equinox.app_1.3.1.R36x_v20100803
30    ACTIVE      devsosgi_1.0.0.qualifier
31    ACTIVE      org.eclipse.ecf.sharedobject_2.2.100.v20101029-1626

Am 30.01.2011 17:52, schrieb Scott Lewis:
Hi Martin,

To help diagnose could you present the output if you launch with the OSGi console turned on (command line parameters -console -consoleLog set)...and in the OSGI console type 'ss'?

The reason I ask...it's possible for either of the providers that they are either not present or can't be started (e.g. because their dependencies aren't satisfied), and it would be useful to see the list of bundles present in your runtime...and their current state.

Also...are you using the OSGi remote services implementation? If so, have you verified that the two bundles org.eclipse.ecf.osgi.services.discovery and org.eclipse.ecf.osgi.services.distribution are included (and started)?

Scott


On 1/30/2011 8:04 AM, Martin Petzold wrote:
Am 30.01.2011 16:51, schrieb Martin Petzold:
Hi,

I have a really strange problem. If i use my launch configuration in eclipse my remote service registration and discovery works fine. Now I have built a product from this launch configuration (all of the bundles are startet) and when I start it (Windows Vista, non-administrator User) remote service registration and discovering just doesn't do anything, also now error or exceptions.

Should I create the containers by hand?
Distribution provider is r-OSGi and discovery provider JmDNS.
_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev

_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev


--
Martin Petzold

Martinsfeld 14
D-50676 Köln
Deutschland

Telefon: +49 (0)221 / 2595961
Mobil: +49 (0)179 / 9220154

Blog: www.zetablog.de



Back to the top