| RE: [cosmos-dev] OSGi DC from command line |
|
What version of java are you running? Can you do a 'props'
on the osgi console to check?
Cheers,
Joel The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
From: cosmos-dev-bounces@xxxxxxxxxxx
[mailto:cosmos-dev-bounces@xxxxxxxxxxx] On Behalf Of Todd, John
A
Sent: Tuesday, July 31, 2007 3:23 PM To: Cosmos Dev Subject: [cosmos-dev] OSGi DC from command line I’m trying to get the DC framework
running from the command line (outside of eclipse) Here’s what I get from
‘ss’ osgi>
ss Framework is
launched. id
State Bundle 0
ACTIVE
org.eclipse.osgi_3.3.0.v20070530 1
ACTIVE
org.apache.xerces_2.8.0.v200606131651 3
ACTIVE
org.apache.xerces_2.8.0.v200704181622 4
ACTIVE
org.eclipse.equinox.preferences_3.2.100.v20070522 5
ACTIVE
org.apache.xml.resolver_1.1.0.v200702082200 8
ACTIVE
org.eclipse.core.contenttype_3.2.100.v20070319 10
ACTIVE
org.apache.derby.core_10.2.2.0 11
ACTIVE
org.eclipse.equinox.common_3.3.0.v20070426 12
ACTIVE
org.mortbay.jetty_5.1.11.v200705231735 13
ACTIVE
org.eclipse.core.jobs_3.3.0.v20070423 14
ACTIVE
org.eclipse.equinox.registry_3.3.0.v20070522
Fragments=23 15
ACTIVE
muse.osgi.soa.mini_2.2.0 16
ACTIVE
javax.servlet_2.4.0.v200705291052 18
ACTIVE
org.apache.muse.complete_2.2.0 19
ACTIVE
org.eclipse.equinox.http.servlet_1.0.0.v20070523 21
ACTIVE
org.w3c.dom_1.3.3.v200704190547 23
RESOLVED
org.eclipse.core.runtime.compatibility.registry_3.2.100.v20070316
Master=14 24
ACTIVE
org.eclipse.osgi.services_3.1.200.v20070531 25
ACTIVE
org.eclipse.equinox.ds_1.0.0.v20070226 26
ACTIVE
org.apache.commons.logging_1.0.4.v200705231731 27
ACTIVE
org.eclipse.core.runtime_3.3.100.v20070530 28
ACTIVE
org.eclipse.equinox.http.jetty_1.0.0.v20070530 29
ACTIVE
org.eclipse.core.runtime.compatibility.auth_3.2.100.v20070502 30
ACTIVE
org.eclipse.cosmos.dc.sample.configurations_1.0.0 31
ACTIVE
org.eclipse.cosmos.dc.local.registry_1.0.0 32
ACTIVE
org.eclipse.cosmos.dc.remote.wsdm_1.0.0 33
ACTIVE
org.eclipse.cosmos.tptp.dependencies_1.0.0 34
ACTIVE
org.eclipse.cosmos.dc.mgmt.common_1.0.0 36
ACTIVE
org.apache.ibatis_2.3.0 37
ACTIVE
org.eclipse.cosmos.dc.common_1.0.0 40
ACTIVE
org.eclipse.cosmos.dc.local.domain_1.0.0 41
ACTIVE
org.apache.xml.resolver_1.1.0.v200705310020 42
ACTIVE
org.apache.xerces_2.8.0.v200705301630 44
ACTIVE
org.eclipse.cosmos.dc.tptp.gla.components_1.0.0 45
ACTIVE wsdl4j_1.6.1 46
ACTIVE
org.apache.xalan_2.7.0 47
RESOLVED
org.eclipse.cosmos.dc.sample.jpa_1.0.0 49
ACTIVE
javax.saaj.api_1.3.0 50
ACTIVE
org.apache.commons.httpclient_3.0.1 51
ACTIVE
javax.mail.api_1.4.0 52
ACTIVE
org.apache.commons.logging_1.1.0_1.1.0 55
ACTIVE
org.eclipse.equinox.app_1.0.0.v20070423 57
ACTIVE
org.eclipse.cosmos.dc.spec_1.0.0 58
RESOLVED
org.eclipse.cosmos.dc.sample.components_1.0.0 59
ACTIVE
org.eclipse.cosmos.dc.mgmt.wsdm_1.0.0 osgi> dc list
assemblies No Runtime
Available This ‘ss’ matches (in version
matching anyway) an ‘ss’ that I do from my eclipse
console. so dc.common got loaded ok, but
there are few problems with some of the bundles spelled out in the attached
error log. I find that went I run ‘test_osgi’
from eclipse, it generates a config.ini which is backwards from what I would’ve
expected, but anyway I would have expected to be able to just take that
config.ini and run with in, but doing that gives mostly ‘invalid bundle’
messages. If anybody has any cycles to help me
get through my configuration troubles I would appreciate
it. Thanks. - John |