ApacheCon US 2010 - Come learn about Tuscany and SCA and meet some of the core project developers

Want to learn more about Apache Tuscany and SCA ? Come to join us at ApacheCon Atlanta, attend the Apache Tuscany Track sessions (Thursday, Nov 4th) and met some of the core project developers.

Building applications with Apache Tuscany
Jean-Sebastien Delfino

Building Cloud Native software
Paul Fremantle

SCA Reaches the Cloud
Jean-Sebastien Delfino

Building RESTful services using SCA and JAX-RS
Luciano Resende

High performance cloud-enabled SCA runtimes
Jean-Sebastien Delfino

Photark/Tuscany Integration
Avdhesh Yadav

Apache Tuscany SCA Java 2.0-M5.1 released

The Apache Tuscany team is pleased to announce the 2.0-M5.1 release of the Java SCA 2.0 project.

Apache Tuscany/SCA provides a runtime environment based on Service Component Architecture (SCA), which is a set of OASIS specifications aimed at simplifying SOA application development. The main purpose of this minor release is to fix the Tuscany Runtime to restore support for running SCA applications in the Google AppEngine environment.

See the RELEASE_NOTES and CHANGES file for more details about the release, and to download the distributions please go to:

http://tuscany.apache.org/sca-java-2x-releases.html

To find out more about OASIS Open CSA go to:

http://www.oasis-opencsa.org

Apache Tuscany welcomes your help. Any contribution, including code, testing, contributions to the documentation, or bug reporting is always appreciated. For more information on how to get involved in Apache Tuscany visit the website at:

http://tuscany.apache.org

Thank you for your interest in Apache Tuscany!

Tuscany related sessions at JavaOne 2010

Some of us will be at JavaOne this year, and we will be presenting
two Tuscany related sessions :

S314011 - Developing composite applications for the Cloud using Apache Tuscany
Wednesday, September 22, 11:30AM

Today's cloud environments pose new challenges for application
developers: hiding cloud infrastructure from business logic,
assembling components on heterogeneous and distributed cloud
environments, and optimizing the provisioning of the required cloud
resources. This session will demonstrate how to use Apache Tuscany and
the Service Component Architecture (SCA) to develop, build, and run an
application composed of several service components in a distributed
cloud environment. We'll illustrate how to encapsulate cloud
infrastructure services as SCA components to simplify the construction
and assembly of the application and how to move components around and
rewire the application to adjust to new business and cloud deployment
conditions.


S313731 - Databinding Unleashed for Composite Applications
Tuesday, September 21, 8:00AM

Data bindings such as JAXB, SDO, DOM, and JSON denote how business
data is represented. Collaborating components in a composite
application often need to use different data bindings as required by
the business logic or protocol stacks. Apache Tuscany provides a
framework that allows mixing and matching of data bindings so that
application developers can have the freedom to choose their preferred
data binding technology without worrying about complex data
transformations. This session is for developers looking for
flexibility of data bindings in the enterprise. Attendees will learn
about: * Decoupling data bindings between service consumers and
providers * Tuscany?s approach to transform data without the
intervention from application code


If you are going to be around, stop by and introduce yourself...

Tuscany SVN structure has changed...

In order to simplify the Tuscany SVN structure and make it easier for users to find the active sub-projects the Tuscany community have changed the SVN structure as described below:

SCA 2.x

For SCA 2.x, which is based on the most recent drafts of OASIS SCA Specifications 1.1, you can find all the code (trunk, branches, tags, contrib) at [1], the SCA 1.x trunk is available at [2].

[1] https://svn.apache.org/repos/asf/tuscany/sca-java-2.x/
[2] https://svn.apache.org/repos/asf/tuscany/sca-java-2.x/trunk/

SCA 1.x

For SCA 1.x, which is based on the OSOA SCA Specifications 1.0, you can find all the code (trunk, branches, tags, contrib) at [3], the SCA 1.x trunk is available at [4].

[3] https://svn.apache.org/repos/asf/tuscany/sca-java-1.x/
[4] https://svn.apache.org/repos/asf/tuscany/sca-java-1.x/trunk

SDO

You can find all SDO code (trunk, branches, tags, contrib) at [5], the SDO trunk is available at [6] and the SDO Community Tests are now available at [7]

[5] https://svn.apache.org/repos/asf/tuscany/sdo-java/
[6] https://svn.apache.org/repos/asf/tuscany/sdo-java/trunk/
[7] https://svn.apache.org/repos/asf/tuscany/sdo-java/trunk-cts/

DAS

You can find all DAS code (trunk, branches, tags, contrib) at [8] and the das trunk is available at [9].

[8] https://svn.apache.org/repos/asf/tuscany/das-java/
[9] https://svn.apache.org/repos/asf/tuscany/das-java/trunk/

Migrating your local checkouts

If you want to point your local svn checkout to the new source location, you could use svn switch :

cd [your local checkout]
svn switch [your new code location in svn]

Please send us an e-mail on the Tuscany mailing lists if you have questions and/or comments.

ApacheCon 2009 Session: Applying OSGi after the fact

ApacheCon US 2009 is almost finished, and I'm done with my last Apache Tuscany/OSGi session.

Tuscany: Applying OSGi modularity after the fact
Fri, 06 November 2009 11:15 by Luciano Resende

Slides are now available

Tuscany Sessions at ApacheCon US 2009

ApacheCon US 2009 is just around the corner, and we are going to have several Apache Tuscany related sessions.

SCA, Java EE, Spring and Web 2.0 Come Together - Service assembly with Apache Tuscany SCA
Wed, 04 November 2009 11:00, by Luciano Resende

Apache Tuscany provides an easy-to-use open source services infrastructure for building, assembling, deploying and running SOA solutions based on the Service Component Architecture (SCA) specifications from OASIS. The Apache Tuscany project goes beyond the SCA specification and is an environment for innovative ideas around SOA, for example it extends SCA to work with web2.0 and OSGI. Apache Tuscany is integrated with other Apache technologies such as Tomcat, Axis2, Geronimo, BSF, Ode, XMLBeans and Abdera.This talk will provide a short overview of SCA and the Apache Tuscany project and will mainly focus on an enterprise integration example to demonstrate how to take advantage of SCA and Tuscany to describe, assemble and deploy an end-to-end SOA solution.

This talk is directed at those who are building distributed solutions from connected services and want to understand how SCA can help.

The presenters will use their experience of working with the Apache Tuscany project and its users to illustrate:
• Partitioning of the application into components and services
• Exploitation of a variety technologies to implement components including Java EE, Spring and Web2.0
• Use of different communication technologies such as web services, JSON-RPC
• Configuration of policy to control consistent quality of service across the distributed application
• Deployment to distributed runtimes with varying capabilities including Java EE containers, web browsers and command line JSE nodes

Distributed OSGi with SCA using Apache Tuscany
Wed, 04 November 2009 13:30 by Raymond Feng

OSGi goes beyond service invocations in a single JVM with the introduction of RFC 119 - Distributed OSGi. It will enable an OSGi bundle deployed in a JVM to invoke a service (either OSGi or non-OSGi) in another JVM or process, potentially on a remote computer accessed via a network protocol. Meanwhile, an OSGi service deployed in another JVM or a non-OSGi program such as Web Service client, potentially on a remote computer, to find and access a service running in the "local" OSGi JVM (i.e. an OSGi deployment can accept service invocations from remote OSGi bundle or external environments). The distributed computing functionality is added to the OSGi programming model without additional APIs or concepts as the distribution layer will be mostly transparent to OSGi developers by configuration.

SCA (Service Component Architecture) provides a technology-neutral approach to abstract business logic into components and assemble them into composite applications. It greatly simplifies the component communications using declarative bindings. QoS requirements can be uniformly declared as SCA intents which can be mapped and realized using different stacks. SCA is a great fit to be a distribution provider for distributed OSGi.

Apache Tuscany is an open source project that implements the SCA specifications. It provides integrations of implementation types (such as Java, Scripting, BPEL, Spring, OSGi and JEE) and binding types (such as Web Service, JMS, EJB, CORBA, RMI, JSONRPC, and ATOM) as the infrastructure for SCA programming. The latest version of Tuscany runtime is fully built on top of OSGi as the foundation. We recently added the OSGi RFC 119 support.

In this session, we will teach you how to develop a distributed OSGi application to leverage the SCA capabilities using Apache Tuscany. A calculator scenario will be used to demonstrate the distributed OSGi service invocations using RMI and Web Service protocols. We will also explain how to model an OSGi bundle as an SCA component and configure the SCA composite to provide communications between services. The readers will understand the basic ideas behind distributed OSGi in the concrete example and the power of Tuscany SCA for service composition.

Tuscany: Applying OSGi modularity after the fact
Fri, 06 November 2009 15:00 by Luciano Resende

Apache Tuscany is an open source project that simplifies the development, deployment and management of distributed applications built as compositions of service components.It is based on the Service Component Architecture specifications being defined by the OASIS Open SCA Collaboration. Tuscany was built with a modular architecture, using a different approach from that of OSGi. In 2008 an effort was started to integrate Tuscany with OSGi. As part of this we undertook an investigation into how to apply OSGi modularity to the Tuscany runtime so that clean boundaries between modules are enforced and different versions of the same library can coexist.This involved analyzing the existing Tuscany modularity which turned up lots of interesting information about the linkages between the various sub-components. This understanding was then used to determine how to map Tuscany into a suitable form for use as OSGi bundles, including prototyping various levels of decomposition granularity. This presentation will share the experiences of analyzing and modularizing an existing project using OSGi. It will discuss what to expect when approaching modularizing existing projects, the tools (and it's caveats) for aiding analysis and also best practices for applying OSGi modularity. Beyond the OSGi enablement for the runtime, we are also going to cover how to integrate OSGi and SCA at the application level.

Tuscany Java SCA 1.5.1 Released

The Apache Tuscany team are pleased to announce the 1.5.1 release of the
Java SCA project.

Apache Tuscany provides a runtime environment based on the Service
Component Architecture (SCA). SCA is a set of specifications aimed at
simplifying SOA application development. These specifications are
being standardized by OASIS as part of the Open Composite Services
Architecture (Open CSA).

This 1.5.1 release is a maintenance release over the previous releases
and includes numerous bug fixes and enhancements, see the
RELEASE_NOTES and CHANGES file for details, and to download the
distributions please go to:

http://tuscany.apache.org/sca-java-releases.html

To find out more about OASIS Open CSA go to:

http://www.oasis-opencsa.org

Apache Tuscany welcomes your help. Any contribution, including code,
testing, contributions to the documentation, or bug reporting is
always appreciated. For more information on how to get involved in
Apache Tuscany visit the website at:

http://tuscany.apache.org

Thank you for your interest in Apache Tuscany!

Article: Design and develop SCA components using the Spring Framework, Part 1: The trifecta: Spring, SCA, and Apache Tuscany

Nice article from "Ramkumar Ramalingam", a member of the Tuscany Community.

In this "Design and develop SCA components using the Spring Framework" series, learn how Service Component Architecture (SCA) and the Spring Framework effectively combine to build distributed service applications. This first article outlines the benefits of combining SCA and Spring. Learn how to design and develop your SCA components using the Spring Framework, how to expose Spring beans as an SCA service, and how to access SCA services and properties within your Spring applications. The example in this article uses the Apache Tuscany SCA Java™ technology runtime.

Read full article...

Variant of Store scenario up and running in Google App Engine !!!

A variant of the Store scenario is now deployed as a distributed application in Google App Engine. The scenario consist of a fruit catalog hosted as one appengine application (tuscany-store-catalog) and the front end ui is hosted as another appengine application (tuscany-store) that has a catalog aggregator used to aggregates multiple catalog references using the JSON-RPC binding. Note that we can easily add new new catalog references hosted either in another appengine applications or other could types.



Note that this is all based on the new Tuscany 2.x runtime, which is based on the OASIS SCA 1.1 draft specifications.

If you got interested, the store and store-catalog applications are available in the sca cloud tutorial sandbox.

Hopefully I can soon post more news of a more heterogeneous cloud scenario working.

Tuscany SCA helloworld-jsp is up and running on Google App Engine

I managed to get an variant of Tuscany SCA helloworld-jsp working on Google App Engine. The application is now up and running at [1]. The composite contains implementation.java, implementation.web and a JSP using SCA taglibs.

During the bring-up, I made a few minor changes to Tuscany 2.x code base to fix the two classes that break the the App Engine JRE Class White List:

* org.apache.tuscany.sca.node.impl.NodeImpl (java.lang.management.ManagementFactory is restricted)
* org.apache.tuscany.sca.core.invocation.impl.JDKProxyFactory (subclassing java.lang.reflect.Proxy is not allowed: org.apache.tuscany.sca.core.invocation.CachedProxy)

I have checked in the fixes into trunk and the application into my sandbox at [2]. After checkout, you can run "mvn" to copy the Tuscany jars into the war/WEB-INF/lib folder. Then you can load the project into Eclipse if you have the Google App Engine Eclipse plugin is installed (See [3]).

We can try to get Web Service binding working as the next step.

[1] http://scacloud.appspot.com/
[2] http://svn.apache.org/repos/asf/tuscany/sandbox/rfeng/helloworld-jsp-google-appengine/
[3] http://code.google.com/appengine/docs/java/tools/eclipse.html#Installing_the_Google_Plugin_for_Eclipse

Article: Communication Flexibility Using Bindings

Take a look at this article written by some members of the "Tuscany Community"

This article is taken from the book Apache Tuscany in Action. It looks at how bindings are used to configure wire protocols for a component's service connections. One of the most important features of SCA is its support for a wide variety of communication protocols. If your services need to talk Web Services, JMS, CORBA, RMI, or REST, they can do it using SCA and Tuscany. If they need to use some specialized or proprietary protocol to meet a particular application need, that's fine too. Even better, your business code doesn't need to know which protocol it's using; the choice of a protocol is made by (you guessed it) the component's configuration. How cool is that? The piece of SCA magic that makes all this possible is called a binding.

In this article, we'll see how to use bindings on services and references, and what it means if no bindings are configured. Finally we'll take a look at the SCA domain and see how bindings relate to communication within and outside an SCA domain.

Apache Tuscany SCA Java 1.5 Released

The Apache Tuscany team are pleased to announce the 1.5 release of the
Java SCA project.

Apache Tuscany provides a runtime environment based on the Service
Component Architecture (SCA). SCA is a set of specifications aimed at
simplifying SOA application development. These specifications are
being standardized by OASIS as part of the Open Composite Services
Architecture (Open CSA).

This 1.5 release is a maintenance release over the previous releases
and includes numerous bug fixes and enhancements, see the
RELEASE_NOTES and CHANGES file for details, and to download the
distributions please go to:

http://tuscany.apache.org/sca-java-releases.html

To find out more about OASIS Open CSA go to:

http://www.oasis-opencsa.org

Apache Tuscany welcomes your help. Any contribution, including code,
testing, contributions to the documentation, or bug reporting is
always appreciated. For more information on how to get involved in
Apache Tuscany visit the website at:

http://tuscany.apache.org

Thank you for your interest in Apache Tuscany!

Tuscany/SCA Sessions at JavaOne 2009

Raymond Feng and Luciano Resende are going to be presenting two Tuscany/SCA sessions at JavaOne 2009, please see below for detailed schedule and links to abstract.

Wednesday June 03 8:45 PM - 9:35 PM Hall E 133

BOF-4760: SCA; JavaT Platform, Enterprise Edition (Java EE Platform); Spring; and Web 2.0 Come Together: Service Assembly with Apache Tuscany SCA


Friday June 05 12:10 PM - 1:10 PM Esplanade 304-306

TS-4846: Building Asynchronous Services with Service Component Architecture

If you are coming to JavaOne, welcome to our sessions!

Runing Tuscany Android Sample Applications

In Apache Tuscany, we have been experimenting with Google Android Platform to build Mobile SOA Applications, and we now have couple Android based samples that demonstrate a Android mobile application consuming SCA services available on the cloud.

Store-android: A front end to our "Store Getting Started Guide" that consumes the catalog and shopping cart services and allow you to shop for fruits and vegetables.

SCATour-android: A front end to the "SCA Tour" scenario that allows you to search for trips direct from your Android phone.

If you are reading here, you are interested on this topic and might want to get hands-on and run this applications... below are the necessary steps to get the Tuscany/Android sample applications running:

1) Install Android SDK following the steps described in Android SDK Installation Guide:


curl -O http://dl.google.com/android/android-sdk-mac_x86-1.5_r2.zip
unzip android-sdk-mac_x86-1.5_r2.zip


2) Install Android Eclipse Plugins (Android DDMS and Android Development Tools):

- Start Eclipse, then select Help > Software Updates....
- In the dialog that appears, click the Available Software tab.
- Click Add Site...
- Enter the Location below and click Ok:
https://dl-ssl.google.com/android/eclipse/
- Back in the Available Software view, you should see the plugin listed by the URL, with "Developer Tools" nested within it. Select the checkbox next to Developer Tools and click Install...
- On the subsequent Install window, "Android DDMS" and "Android Development Tools" should both be checked. Click Next.
- Read and accept the license agreement, then click Finish.
- Restart Eclipse.

3) Create a Android Virtual Device (AVD)


cd ~/opt/android-sdk-mac_x86-1.5_r2/tools
android create avd --name android-1.1 --target 1
android create avd --name android-1.5 --target 2


4) Configure the Android Eclipse Plugins to point to the Android SDK

- Start Eclipse, then select Eclipse->Preferences->Android
- Point to the directory where you installed the Android SDK in step 1.




You you should be ready to run Android applications. Now let's add the Tuscany Android samples to your Eclipse IDE and run it.

1) Checkout Tuscany code and create Eclipse IDE project for the samples we are going to use :


svn co http://svn.apache.org/repos/asf/tuscany/sca-java-1.x/trunk/ java-1.x
cd java-1.x/samples/store
mvn eclipse:eclipse


2) Import the sample projects into Eclipse

- Start Eclipse
- Select File->Import : General->Existing Projects into Workspace
- Select root directory : java-1.x/samples/store
- Select File->Import : General->Existing Projects into Workspace
- Select root directory : java-1.x/samples/store-android

3) Launch the store sample application

- In eclipse project (sample-store), run the Launch.java as a Java Application

4) Launch the store android application

- In eclipse project (sample-store-android), run the project as a Android Application


You should now have your Android Fruit Store up and running, accessing the Catalog and Shopping Cart services from the regular store application we have started in step 3.



















References:
- Tuscany Getting Started Guide : The Fruit Store Application scenario.


I also want to give the special Thanks to our 2009 GSoC Student, Lookman SANNI, for the recent updates to the Store-Android sample and ui.

Java SCA 2.0-M1 release post at InfoQ

The Apache Tuscany team announced the release of 2.0 M1 of the Java Service Component Architecture (SCA) project. SCA defines a technology neutral component and assembly model for business application developers to focus on implementing the business logic and composing them into business solutions without worrying about the technology concerns. The latest version of SCA is being standardized at OASIS as part of Open Composite Service Architecture(Open CSA).

Apache Tuscany SCA 2.0 M1 Released

The Apache Tuscany team are pleased to announce the 2.0 M1 release of
the Java SCA project.

Apache Tuscany provides a runtime based on the Service Component
Architecture (SCA) which is a set of specifications aimed at
simplifying SOA Application Development. The SCA specifications are
being standardized at OASIS as part of the Open Composite Services
Architecture (Open CSA).

The Apache Tuscany SCA 2.0-M1 release is the first milestone on the
road to a full Apache Tuscany SCA 2.0 release. The goal of Apache
Tuscany SCA 2.0 is to provide an OSGi based SCA runtime that is
compliant with the OASIS SCA specifications.

With this first milestone release, a solid OSGi foundation is in place
to support the development, build, testing and deployment of Tuscany
modules and extensions following OSGi best practices. The first steps
have also been taken to incorporate the latest OASIS SCA draft
specifications.

In subsequent milestone releases the compliance gap with the OASIS
specifications will continue to be narrowed and, now that the OSGi
infrastructure in place, OSGi/SCA integration at the application level
will be explored further.

Feature Overview
----------------

The Apache Tuscany SCA 2.0-M1 release includes implementations of the
main SCA specifications and some recent updates from Open CSA drafts including:

* SCA Assembly Model V1.0
* SCA Policy Framework V1.0
* SCA Java Common Annotations and APIs V1.0
* SCA Java Component Implementation V1.0
* SCA Web Services Binding V1.0

It also includes implementations of features not yet defined
by SCA specifications, including:

* SCA bindings for RMI.
* Databindings for JAXB, Axis2's AXIOM, DOM, SAX and StAX

In milestone one Tuscany SCA supports the following host-deployment options: -

* running standalone
* running in a OSGi enabled runtime Environment (Equinox)
* running with distributed nodes across multiple JVMs but
without domain configuration support

For full details about the release and to download the distributions
please go to:

http://tuscany.apache.org/sca-java-2x-releases.html

Apache Tuscany welcomes your help. Any contribution, including code,
testing, contributions to the documentation, or bug reporting is
always appreciated. For more information on how to get involved in
Apache Tuscany visit the website at:

http://tuscany.apache.org/

Thank you for your interest in Apache Tuscany!

The Apache Tuscany Team.

Apache Tuscany SCA Java 1.4 Released

The Apache Tuscany team are pleased to announce the 1.4 release of the Java SCA project.

Apache Tuscany provides a runtime environment based on the Service Component Architecture (SCA). SCA is a set of specifications aimed at simplifying SOA application development. These specifications are being standardized by OASIS as part of the Open Composite Services Architecture (Open CSA).

The Tuscany SCA Java 1.4 release adds various improvements including:

* Support for Spring version 2.5.5
* Support for Implementation Policies and SCA Annotations for Spring beans
* Support for Axis2 version 1.4.1
* Support for Axis2 MTOM message optimization
* Support for Aspect Oriented Tracing
* Support for SCA callbacks with JMS binding
* Support for @requestConnection / @responseConnection with JMS binding
* Improved user guide documentation
* A new Corba Binding (GSoC) Extension
* A new GData Binding (GSoC) Extension
* Tuscany Eclipse Plugins enhancements to be compatible with new Eclipse Ganymede release
* Improved simple-bigbank-spring samples to demonstrate various SCA bindings with Spring

and numerous bug fixes. see the RELEASE_NOTES and CHANGES file for details, and to download the distributions please go to:

http://tuscany.apache.org/sca-java-releases.html

To find out more about OASIS Open CSA go to:

http://www.oasis-opencsa.org

Apache Tuscany welcomes your help. Any contribution, including code, testing, contributions to the documentation, or bug reporting is always appreciated. For more information on how to get involved in Apache Tuscany visit the website at:

http://tuscany.apache.org

Thank you for your interest in Apache Tuscany!

Article: Deploy an SCA application using the Tuscany domain manager

This article gives you an introduction to the Tuscany domain manager and describe how you would go about using it to deploy and run SCA Applications.

The components in an SCA composite application can run on different nodes in a network. In Apache Tuscany, an SCA domain can be used to administer a set of nodes. In SCA, the definitions of composites, components, their implementations, and the nodes they run on belong to what's called an SCA domain. SCA implementations like Tuscany provide administration tools that let a system administrator manage the SCA artifacts in the domain. Using the domain gives you the flexibility to specify installation characteristics of nodes, such as host or port, at the time the nodes are added to the domain instead of in composite files. This article demonstrates how an application comprised of a number of SCA components can be administered via an SCA domain. Learn each step involved in adding an SCA application to the domain.

The example you use in this article is the store application from the "Getting started with Tuscany" guide (see the Resources section for a link). While the "Getting started with Tuscany" guide uses Eclipse to deploy the application, this article shows you how to run the same application in a real production environment. This article illustrates the required steps using an application that you can run in stand-alone Tuscany run time without additional middleware requirements.

Article: An overview of the Service Component Architecture feature pack

IBM has recently announced the "WebSphere Application Server Feature Pack for SCA" that uses Apache Tuscany. Below is an overview article that introduces the SCA FEP and SCA in general.

An introduction to open Service Component Architecture (SCA) concepts, objectives of the technology, and highlights of some key integration points that provide great value to IBM® WebSphere® Application Server V7 users.

PR : Apache Tuscany enables service oriented architecture solutions to more easily respond to new business requirements.

Apache Tuscany, a new Top-Level Project of the Apache Software Foundation (ASF), today announced the release of version 1.3.2 of its Service Component Architecture (SCA) for Java – the Project's latest release since its graduation from the ASF Incubator four months ago.