Differences between revisions 6 and 7
Revision 6 as of 2006-05-12 13:12:54
Size: 1654
Editor: edslattery
Comment:
Revision 7 as of 2009-09-20 22:47:30
Size: 1654
Editor: localhost
Comment: converted to 1.6 markup
No differences found!

J2SE Classpath Configuration

Tuscany applications can be run in a J2SE 5.0 environment. Before you can run Tuscany applications in that environment, the Tuscany runtime JAR files and the JAR files they depend on must be added to your J2SE classpath.

Add the following JAR files to the classpath:

sca-api-SNAPSHOT.jar
sdo-api-SNAPSHOT.jar
tuscany-common-SNAPSHOT.jar
tuscany-core-SNAPSHOT.jar
tuscany-model-SNAPSHOT.jar
tuscany-container-java-SNAPSHOT.jar
tuscany-sdo-impl-SNAPSHOT.jar
axis-wsdl4j-1.2.jar
asm-2.2.jar
common-2.2.0-I200602160000.jar
ecore-2.2.0-I200602160000.jar
ecore-change-2.2.0-I200602160000.jar
ecore-xmi-2.2.0-I200602160000.jar
xsd-2.2.0-I200602160000.jar

The EMF JAR files are required by the SDO runtime.

If you're planning to use SCA Web Service bindings from your Tuscany application, add the following JAR files to your classpath:

tuscany-binding-axis2-SNAPSHOT.jar
axis2-core-0.94.jar
commons-codec-1.3.jar
commons-httpclient-3.0.jar
commons-logging-1.0.4.jar
log4j-1.2.12.jar
stax-api-1.0.jar
ws-policy-SNAPSHOT.jar
wstx-asl-2.8.2.jar

Application Programming

Application code that wishes to use SCA services must first start the Tuscany runtime. Then the application code can access the module context in the normal way using the CurrentModuleContext API

TuscanyRuntime tuscany = new TuscanyRuntime("hello", null);
tuscany.start();

ModuleContext ctx = CurrentModuleContext.getContext();
MyService service = (MyService) ctx.locateService("serviceName");
service.doStuff(...);

tuscany.stop();

Tuscany/TuscanyJava/J2SESetup (last edited 2009-09-20 22:47:30 by localhost)