Hi,
I just added a new module node-launcher-equinox to launch SCA Node using
Equinox. It requires:
tuscany-node-launcher-equinox-1.4-SNAPSHOT.jar
app-1.0.0-v20070423.jar
common-3.3.0-v20070426.jar
contenttype-3.2.100-v20070319.jar
jobs-3.3.0-v20070423.jar
osgi-3.3.0-v20070530.jar
preferences-3.2.100-v20070522.jar
registry-3.3.0-v20070522.jar
runtime-3.3.100-v20070530.jar
Thanks,
Raymond
--------------------------------------------------
From: "Jean-Sebastien Delfino" <[EMAIL PROTECTED]>
Sent: Wednesday, August 27, 2008 5:43 PM
To: <[email protected]>
Subject: Re: How to build a Tuscany OSGi environment?
Raymond Feng wrote:
I see two lists here:
1) A list of jars required to run the node-launcher-osgi (assuming it's
under tuscany\launcher)
tuscany-node-launcher-osgi-1.4-SNAPSHOT.jar
org.apache.felix.framework-1.0.4.jar
org.osgi.compendium-1.0.1.jar
org.osgi.core-1.0.1.jar
org.osgi.foundation-1.0.0.jar
servlet-api-2.5.jar
2) A list of OSGi bundles required to start a SCA node (assuming it's
under tuscany\modules or tuscany\lib)
This varies depending on what extensions are required. This can be one of
the distros + tuscany-extensibility-osgi-1.4-SNAPSHOT.jar (if not added
to the distro)
Then we could run the following command:
java -Djava.ext.dirs=.\tuscany\launcher -DTUSCANY_HOME=.\tuscany -jar
.\tuscany\launcher\tuscany-node-launcher-osgi-1.4-SNAPSHOT.jar ...
Thanks,
Raymond
--------------------------------------------------
From: "Jean-Sebastien Delfino" <[EMAIL PROTECTED]>
Sent: Wednesday, August 27, 2008 3:03 PM
To: <[email protected]>
Subject: Re: How to build a Tuscany OSGi environment?
Seems like we keep going around my question :) some comments inline.
Raymond Feng wrote:
There are a few options on the table now:
1) Unzip one of the binary distros from Tuscany into TUSCANY_HOME
AFAIK no Tuscany distro includes node-launcher-osgi at the moment, so
'Unzip one of the binary distros' is not getting me very far.
2) Use maven dependency plugin to copy project dependencies to
TUSCANY_HOME (see the node-launcher-osgi/pom.xml).
Did that, I get that list of JARs:
tuscany-extensibility-osgi-1.4-SNAPSHOT.jar
tuscany-node-launcher-osgi-1.4-SNAPSHOT.jar
org.osgi.core-1.0.1.jar
org.osgi.compendium-1.0.1.jar
org.osgi.foundation-1.0.0.jar
org.apache.felix.framework-1.0.4.jar
PS: If you use our tuscany-maven-osgi-junit plugin, it will create the
bundles automatically from the maven dependency list.
Sorry, I'm having trouble understanding what that means. Aren't the
Tuscany JARs OSGi bundles already?
We don't have a very good story yet. Any ideas are welcome.
I know, I'm trying to help with ideas too, but to help I need answers to
my simple questions :) I'm going to try to ask my question again
differently, hoping it works this time.
1) Is this list of JARs:
tuscany-extensibility-osgi-1.4-SNAPSHOT.jar
tuscany-node-launcher-osgi-1.4-SNAPSHOT.jar
org.osgi.core-1.0.1.jar
org.osgi.compendium-1.0.1.jar
org.osgi.foundation-1.0.0.jar
org.apache.felix.framework-1.0.4.jar
the minimum set of JARs needed to an OSGi-enabled Tuscany node / Felix?
2) What is the equivalent list of JARs for Equinox?
--
Jean-Sebastien
OK Thanks, I'd like to simplify a bit and not require
the -Djava.ext.dirs=.\tuscany\launcher part. I'll look into the launcher
code to see if that can be done.
I'll add tuscany-extensibility-osgi to the test distro too.
Question (2) remains: What is the equivalent list of JARs for Equinox?
Any idea?
--
Jean-Sebastien
