Luciano Resende

Turntable.FM for the Geeks

2012-01-11T10:21:00.000-08:00

Hopefully, if you are reading this, you have already stumbled upon Turntable.FM, otherwise I really recommend it…

"So what is Turntable.fm? It’s a browser-based chatroom that streams music based on the choices of a rotating cast of DJs drawn from whoever is in the room. There are up to five DJs at any one time who create playlists; the station cycles through the playlists one song at a time, moving from one DJ’s pick to the next, as the room votes on how “lame” to “awesome” the track is. A (sometimes fast-moving) discussion takes place in a chatroom on the bottom right of the screen. DJs get points for picking popular songs and if enough people think a song is lame, it skips to the next. You can upload songs or search through the Medianet-powered library to create your playlist when it’s your turn to DJ." (read more ...)

But, other then the music aspects, Turntable.FM has brought lot's of opportunities for engineers to hack it and extend it. One of the pioneers on extending Turntable.fm was Michael Frick (@mdfrick) which created TurntablePlus a chrome extension that allows users see a variety of extra information from the current music rooms, such as who has "lamed" or "awesomed" your song, who has been afk and for how long, etc.

Another engineer that brought the possibilities to extending Turntable.fm to the next level was Alain Gilbert (@alain_gilbert), which created the "unofficial" Turntable.FM API (source code available in github) and with that, enabled users to create "bots" for Turntable.FM music rooms. One of the first bots that I'm aware of was #Cleopatra (a.k.a cleo), developed by Frick. Initially, Cleopatra main feature was to control the DJ Woooo NoAFK room, and kick anyone that was afk on that room. This is when I got involved with Turntable.FM and with Node.js and created my own bot named #Mermaid, which was usually in DJ Woooo main room, counting awesomes/lames for the djs. Later on, bots started becoming more common, with a variety of functionality such as dj queue management, booting afk people once the room gets to it's capacity, etc

If you are still reading this post, you probably got interested and already have some ideas to create your own extensions or just to start hacking around Turntable.FM, so here are some resources that can help get you started:

Turntable.FM Extensions

- Turntable.Plus
- Turntable Extensions

Turntable.FM Bookmarklets

- AutoBop
- Turntable autobop, autodj, etc

Turntable.FM API and Bots

- Turntable.API (unofficial)
- the BusDriver Bot

Hope you enjoy, and start hacking and extending Turntable.FM.
And look for me (a.k.a.[DJ] Luck) around the Turntable.FM EDM/Mashup rooms, .

Data Layer and Schema Definitions at MongoSV 2011

2011-12-09T18:56:00.001-08:00

Please see below the slides presented today at MongoSV 2011 about Data Layer and Schema Definitions. Title : Data Layer and Schema Definitions

This talk goes over various patterns, techniques and best practices around developing webscale applications using MongoDB. We will cover various techniques including a DSL like schema definition tool, benefits of using data abstraction API, and other best practices we have learned.

Data access layer and schema definitions

View more presentations from Luciano Resende

Building Flexible APIs for Web 2.x/Cloud Applications - JavaOne 2011

2011-12-09T18:51:00.001-08:00

JavaOne 2011 have already finished a couple months ago, but it's never too late to share the presentation materials.

Building Flexible APIs for Web 2.x/Cloud Applications (JavaOne 2011 Session 25208)

Using an open and simple API is a great way to build a developer ecosystem and grow a user base dramatically for Web 2.x (social/cloud/mobile) applications. But building flexible APIs can be a challenge. This session covers how to build a nice Web API from scratch, using open source stacks.

It starts with data modeling with a DSL tool and generates POJOs that can be transformed in JSON/XML and persisted with JPA/NoSQL. After defining the service interface, it expands the API experience with REST, JSON-RPC, and other cloud-friendly protocols without application coding. The presentation gets the API running immediately and tests it with a browser. In addition, it addresses how to realize common patterns such as pagination and hypermedia.

Building Flexible APIs for Web 2.x/Cloud Applications (25208)

View more presentations from Raymond Feng

Apache Tuscany SCA Java 1.6.2 released

2011-04-16T17:22:00.000-07:00

The Apache Tuscany team is pleased to announce the 1.6.2 release of the Java SCA project.

Apache Tuscany/SCA provides a runtime environment based on 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 1.6.2 release includes some bug fixes to the previous 1.6.1 release, as described in the RELEASE_NOTES and CHANGES files. To download the distributions, please go to:

http://tuscany.apache.org/sca-java-1x-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!

The Apache Software Foundation Launches "Apache Extras" to Accelerate Innovation

2010-12-15T07:54:00.000-08:00

The Apache Software Foundation and Google have just announced the launch of Apache Extras website.

Apache Extras provides a central place for the great user community to look for Apache related projects that can't be an official Apache project particularly because the license it uses is not compatible with the Apache License.

If you have an Apache Related project already hosted at Google Code, and wish to be part of Apache Extras, just file a ticket with the Google Code infrastructure team to have your project moved. If you are creating a new project related to Apache technologies, you might want to consider Apache Extras for it's home.

More details and answers to your questions are available in our FAQ and User Guidelines.

InfoQ: Service Component Architecture – State of the Union

2010-11-30T11:27:00.000-08:00

Nice to see others embracing and evangelizing about Service Component Architecture (SCA). In this session, Clemens Utschig-Utschig presents the Service Component Architecture (SCA), the component model used, best development practices, and the current status of the specification.

InfoQ: Service Component Architecture – State of the Union

I've been to a A Keysigning Party. Now what ?

2010-11-17T21:06:00.000-08:00

Couple weeks ago, I participate in the "ApacheCon Keysigning Party", and that being my first "party" I was a little lost after the party, and I noticed couple of my friends were feeling the same way.

Well, after some research, I gathered some steps that helped me and hopefully can help you as well.

What's a Keysigning party ?

If you have never been to a "Keysigning Party", you can read more about it here.

The Actual Signing of Keys

The best think to do is to use a tool to help you with the key sign steps. In my case, I've decided to use PGPSigner. See the README to more information about the tool.

Another piece of information you will use is the GPG keyring with all the public keys on the key list. For the purpose of this tutorial, let's call it keysigning-keyring.asc

You also will need your own private key, which you can get it using gpg --export-secret-key -a "User Name" > private.key

Now that you have all the required information, let's launch PGP Signer and sign the keys.


$ pgpsigner.sh 

Welcome to PGPSigner V1.0
PGPSigner> partyring keysigning-keyring.asc
PGPSigner> list
... you should see a list of keys from the partyring ...
PGPSigner> signevent "Keysigning event"
PGPSigner> secretring private.key
PGPSigner> signkey 0xefb55df1
... this is your own key id ...
PGPSigner> unlock
... this will ask for your private key password ...
PGPSigner> sign
PGPSigner> mailserver smtp.domain.org
... this is your smtp server ...
... must allow sending without authentication/authorization ...
PGPSigner> mail
PGPSigner> quit
Goodbye

The steps above will load the keyring, sign keys using your private key, and mail them for the individual owners.

Importing signatures

First, let's check if anyone upload new signatures to a key server with the following command:


$ gpg --recv-keys EFB55DF1
gpg: requesting key EFB55DF1 from hkp server keys.gnupg.net
gpg: key EFB55DF1: "Luciano Resende (Code Signing Key) " 2 new signatures
gpg: no ultimately trusted keys found
gpg: Total number processed: 1
gpg:         new signatures: 2

If you received any keys via e-mail, just detach the .asc file and run the following command:


$ gpg --import 0xefb55df1.asc 
gpg: key EFB55DF1: "Luciano Resende (Code Signing Key) " not changed
gpg: Total number processed: 1
gpg:              unchanged: 1

Submitting your signed key to a key server


$ gpg --send-keys EFB55DF1
gpg: sending key EFB55DF1 to hkp server keys.gnupg.net

Hopefully this will get your next Keysigning Party experience much simpler.

Apache Wink 1.1.2-incubating released

2010-11-17T07:35:00.000-08:00

The Apache Wink project is pleased to announce the release of Apache Wink 1.1.2-incubating.

Apache Wink is a simple yet solid framework for building RESTful Web services. It is comprised of a Server module and a Client module for developing and consuming RESTful Web services.

The Wink Server module is a complete implementation of the JAX-RS v1.1 specification. On top of this implementation, the Wink Server module provides a set of additional features that were designed to facilitate the development of RESTful Web services.

The Wink Client module is a Java based framework that provides functionality for communicating with RESTful Web services. The framework is built on top of the JDK HttpURLConnection and adds essential features that facilitate the development of such client applications.

To download the distributions please go to:

http://incubator.apache.org/wink/downloads.html

Apache Wink 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 Wink visit the website at:

http://incubator.apache.org/wink/

ApacheCon Session: How mentoring programs can help newcomers get started with open source

2010-11-05T07:41:00.000-07:00

View more presentations from Luciano Resende.

How mentoring programs can help newcomers get started with open source
Luciano Resende

ApacheCon Session: Building RESTful services using SCA and JAX-RS

2010-11-05T07:37:00.000-07:00

View more presentations from Luciano Resende.

Building RESTful services using SCA and JAX-RS
Luciano Resende
Jean-Sebastien Delfino

ApacheCon Session: SCA Reaches the Cloud

2010-11-05T07:31:00.000-07:00

View more presentations from Luciano Resende.

SCA Reaches the Cloud
Luciano Resende
Jean-Sebastien Delfino

ApacheCon Session: Building applications with Apache Tuscany

2010-11-04T07:30:00.000-07:00

View more presentations from Luciano Resende.

Building applications with Apache Tuscany
Jean-Sebastien Delfino
Luciano Resende
Simon Laws

Images of Pernambuco - photo exhibition by Jason Gardner at the Brazilian Consulate

2010-10-25T07:45:00.000-07:00

The Consulate General of Brazil in San Francisco presents an exhibition of photographer Jason Gardner’s work documenting the music, dance, culture and ritual of Carnaval in the northeastern state of Pernambuco.

The Beauty of Pernambuco’s Carnaval
Through the Eyes of a Brooklyn Photographer

When: November 11, 2010 - February 11, 2011 (Opening Nov. 10)

Where: Consulate General of Brazil in San Francisco 300 Montgomery Street, Suite 300 San Francisco, CA 94104

“Images of Pernambuco” will take you to a world of magic, colors and movement, within the realm of the Afro-Brazilian cultural experience.

Jason will be attending the exhibit’s opening Wednesday, November 10, from 5:30 to 7:30 PM at the Brazilian Consulate. There will also be live Brazilian music and caipirinhas. The show will continue from November 11 through February 11, 2011 during the Consulate’s usual hours, 9:00 AM to 1:00 PM, Monday to Friday.

Please RSVP to cultural@brazilsf.org

Apache Tuscany SCA Java 2.0-M5.1 released

2010-10-23T19:24:00.000-07:00

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!

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

2010-10-23T18:47:00.000-07:00

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

Google announce : Google Code-In 2010

2010-10-07T13:46:00.001-07:00

Google just announced Google Code-in, an open source development and outreach contest targeted at 13-18 year old students around the world.

Find more info at their blog.

JavaOne 2010 – Developing Composite Applications for the Cloud with Apache Tuscany (SCA)

2010-09-28T22:53:00.000-07:00

Very nice to see positive feedback from our JavaOne 2010 session :

A great take on a great technology, SCA (Service Component Architecture), was given by Jean-Sebastien Delfino (IBM) and Luciano Resende (Shutterfly). Can Tuscany (a SCA implementation) shield you from the complexities of component assembly/component integration/deployment/inter-component communications/client protocols/… in the Cloud? It turns out that many of these problems are not specific to the Cloud, they apply to any distributed environment, but the live demo made it a point to show how SCA works in a Cloud.

Read full article here.

Apache Tuscany & Apache Nuvem slides from JavaOne 2010

2010-09-26T22:46:00.000-07:00

For those that were not able to join us at JavaOne 2010, here are the slides

S314011 - Developing Composite Applications for the Cloud with Apache Tuscany

View more presentations from luckbr1975.

Apache Tuscany & Apache Nuvem related sessions at JavaOne 2010

2010-09-10T22:52:00.000-07:00

I will be at JavaOne this year, and we will be presenting/co-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...

Apache Nuvem

2010-08-25T22:59:00.000-07:00

Apache Nuvem is just getting ramped up as a Apache Incubator project, but it's already making the news with an InfoQ article written by Mark Little (CTO of JBoss at Red Hat).

...So of course if one cloud project is good, two must be better, so what does that make three? We could find out soon, because the Nuvem project may well be going to the Apache incubator stage soon. According to the information available, it will:

* Define an open API that abstracts common cloud platform services to help decouple the application logic from the particulars of a specific proprietary cloud.

* Implement the Nuvem API for popular clouds such as Google AppEngine, Amazon EC2 and Microsoft Azure.

* Initially focus on User Authentication and Authorization, Distributed Cache, Data Store, Queuing; then extend to other services such as Chat, Logging, and Debugging.
...

but the article then goes about putting the Apache Nuvem project at the same layer as Apache Deltacloud and Apache LibCloud.

...
The wiki page also talks about the need for a common API to help avoid vendor lock-in when moving between cloud implementations. As with Deltacloud and libCloud, it seems that Nuvem will target Infrastructure as a Service (IaaS). It is interesting to note that according to the submitters, there is a prototype under development which uses Tuscany, the Apache SCA implementation. So perhaps this effort will go some way to answering the questions around SOA and its relationship to Cloud.
...

So, let me try to reiterate the alignment of Apache Nuvem project with Apache Deltacloud and Apache libCloud as initially described in it's project proposal:

Nuvem complements Apache libCloud and Deltacloud projects (which both cover provisioning and elasticity in the cloud), providing portability of applications and application services across heterogeneous cloud environments.

Apache Nuvem is about creating an Application level API that would abstract the Infrastructure Services available to build applications, like how to access a Data Storage service and store information to the storage; while Apache DeltaCloud and libCloud would provide an API to create the Data Storage and configure it for the application usage.

The current implementation of Nuvem also leverage SCA to simplify how applications can declaratively reconfigure themselves based on the Cloud environment where they are being deployed.

I hope this helps clarify the goals of the Apache Nuvem project, and how it align with Apache Deltacloud and Apache libCloud

Palestra sobre Open Source e Projetos Apache em Cuiabá (16 de Julho)

2010-07-15T04:10:00.000-07:00

Veja abaixo maiores informações e a localidade da palestra de Open Source e Projetos Apache que estarei ministrando em Cuiabá junto com outro Apache Committer (Adriano Crestani)

O Campus Cuiabá do Instituto Federal de Mato Grosso (IFMT) convida os servidores, alunos e comunidade para participarem de uma palestra informal sobre Software Livre (Open Source) e Google Summer of Code nesta sexta-feira, dia 16 de julho, às 09 horas, na sala de projeções, com dois colaboradores da IBM EUA e membros da Apache Software Foundation, Luciano Resende e Adriano Crestani, ambos bacharéis em Ciência da Computação pela Universidade Federal de Mato Grosso (UFMT). A palestra é gratuita.

Os convidados falarão sobre suas experiências no desenvolvimento de softwares Open Source, bem como sobre os desafios vencidos em sua carreira profissional até sua ascensão na IBM EUA. Mais informações sobre a palestra no telefone (65) 3314-3566.

Vacations in Brazil, Open Source and Apache talks, etc

2010-07-11T21:59:00.000-07:00

It's been a while since I last went to Brazil, and it's also good to go back and see family and friends.

I'll take advantage of this opportunity and speak with students of couple of Universities in my hometown about some initiatives that can help them get involved in open source such as Google Summer of Code and Apache Mentoring Program. I'll also spend some time and chat about the projects I'm actively participating, such as Apache Tuscany, Apache PhotArk and the recently created Apache Nuvem; I'm also persuading a friend to come and talk about http://lucene.apache.org/.

If you are around, please make sure to join us... I'll make sure to post more details once I know specific details about date/time.

Apache PhotArk M2-incubating released

2010-05-24T21:24:00.000-07:00

The Apache PhotArk team is pleased to announce the release of Apache PhotArk M2-incubating.

Apache PhotArk will be a complete open source photo gallery application including a content repository for the images, a display piece, an access control layer, and upload capabilities. The idea is to have a rigid design for the content repository with a very flexible display piece. The images in the content repository will be protected with granular access control.

PhotArk gallery currently allows you define and manage a set of albums hosted local into the content repository and provides a default web UI for album navigation. PhotArk also supports creating and deploying your own photo gallery into Google AppEngine cloud infrastructure.

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

http://incubator.apache.org/photark/photark-downloads.html

Apache PhotArk 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 PhotArk visit the website at:

http://incubator.apache.org/photark/

Thank you for your interest in Apache PhotArk!

The Apache PhotArk Team.

Setting up WireShark on Mac OS X

2010-05-07T12:13:00.000-07:00

For those having problems getting WireShark to work on Mac OS, here is a great post from Joseph Lorenzo Hall that gives step-by-step directions and help you get a clean installation working like a charm.

Building RESTFull services with Apache Tuscany, SCA and JAX-RS

2010-05-03T19:17:00.000-07:00

Introduction to Tuscany REST Binding

The Tuscany Java SCA runtime supports Representational State Transfer (REST) services invocations via the extension. Tuscany REST binding leverage JAX-RS Standards based annotations to map business operations to HTTP operations such as POST, GET, PUT and DELETE and utilizes Tuscany Databindings to provide support for different wire formats such as JSON, XML, Binary, etc shielding the application developer from contaminating his business logic with code to handle payload production/transformation details.

Using the Tuscany REST binding

The primary use of the REST binding is to provide business services over HTTP in a distributed fashion. The simplest way to use the REST binding is to declare a business service that can be shared over the web and provide an HTTP address where one can access the service. This service is declared in an SCA composite file.

 
    <component name="Catalog">
 <implementation.java class="services.store.FruitsCatalogImpl"/> 
        <service name="Catalog">
     <tuscany:binding.rest uri="http://localhost:8085/Catalog">
             <tuscany:wireFormat.json />
         <tuscany:operationSelector.jaxrs />
         </tuscany:binding.rest>
    </service>
    </component>

Another way of implementing a REST service is to use a collection interface that matches the actions of the HTTP protocol. In this case, the methods must be named post, get, put, and delete. Tuscany ensures that the proper method is invoked via the request and response protocol of HTTP:


public class TestGetImpl {
    
    public InputStream get(String id) {
        return new ByteArrayInputStream(("<html><body><p>This is the service GET method, item=" + id + "</body></html>").getBytes());

    }
}

So using the common verbs of HTTP and Java object serialization, one can implement services and run them anywhere the HTTP protocol is implemented. The service developer or implementer simply creates methods for post, get, put, and delete, and a business collection such as a shopping cart, telephone directory, insurance form, or blog sites can be created. See the Tuscany module binding-rest-runtime for complete examples.

Mapping business interfaces to HTTP Operations

JAX-RS offers standards based annotations that allow properly configuration of the REST service endpoint and mappings of specific HTTP operations (e.g. get, put, post, delete) to java operations. The following subset of JAX-RS annotations are currently supported :

URI Mappings


@Path
@Path("{id}")
@PathParam("id")

Operation Mappings


@GET
@PUT
@POST
@DELETE

{info}
Integration with a existent JAX-RS engine might help on processing the full set of JAX-RS annotations. I have started looking into leveraging Wink resourceProcessor or related code to help on this layer.
{info}

Wire Formats

This binding will support two styles of wire formats and will be used to control what type of payload will be generated by the service:

- hardWired : where you hard code the wire format expectations in the composite when configuring the binding. In the example below, service will be using JSON payload.


<binding...>
   <wireFormat.json>
</binding...>

- dynamic : based on Content-Type header for request and Accept header for response. In the case below, the request content will be parsed based on the Content-Type request header and the response payload will be based on the request Accept header.


<binding...>
   <wireFormat.dynamic>
</binding...>

Cache control using ETags, Last-Modified and other HTTP Headers

The HTTP specification provides a set of methods for HTTP clients and servers to interact. These methods form the foundation of the World Wide Web. Tuscany implements many of these methods a binding interface to a collection. The main methods are:

* GET - retrieves an item from a collection
* POST - creates or adds an item to a collection
* PUT - updates or replaces an item in a collection
* DELETE - removes an item in a a collection

The HTTP specification (HTTP 1.1 Chapter 13 - Caching) also provides a mechanism by which these methods may be executed conditionally. To perform conditional methods, an HTTP client puts 3 items in the HTTP request header:

* ETag - entity tag, a unique identifier to an item in a collection. Normally created and returned by the server when creating (POST) a new item.
* LastModified - an updated field. Normally a string containing a date and time of the last modification of the item.
* Predicate - a logical test (e.g. IfModified, IfUnmodified) to use with the ETag and LastModified to determine whether to act.

The complete list of predicates is given in the HTTP specification.

The most common use of conditional methods is to prevent two requests to the server instead of one conditional request. For example, a common scenario is to check if an item has been modified, if not changed update it with a new version, if changed do not update it. With a conditional PUT method (using the IfUnmodifed predicate and a LastModified date), this can be done in one action. Another common use is to prevent multiple GETs of an item to ensure we have a valid copy. Rather than doing a second request of a large item, one can do a conditional GET request (using an IfModified predicate and a LastModified date), and avoid the second request if our object is still valid. The server responds with either a normal response body, or status code 304 (Not Modified), or status code 412 (precondition failed).

Default cache control is done by using generated ETags based on response content checksum. To avoid data to be overwriten during concurrent updates, include an HTTP If-Match header that contains the original content ETag value. If you want to force an update regardless of whether someone else has updated it since you retrieved it, then use If-Match: * and don't include the ETag.

{info}
Further support for declarative with possible injection of fields to cache control headers is under investigation.
{info}

Store scenarios goes REST - Catalog Services using binding.rest

Below is our Store Catalog exposed as REST services utilizing the new binding.rest.

Let's start by looking on how the component gets defined and configured in the composite file, particularly the following details :

- binding.rest uri defines the Catalog service endpoint
- wireFormat.json configure the service to use JSON as the payload
- operationSelector.jaxrs configure the binding to use JAX-RS annotations to map the HTTP operations to business operations


<composite xmlns="http://docs.oasis-open.org/ns/opencsa/sca/200912"
  xmlns:tuscany="http://tuscany.apache.org/xmlns/sca/1.1"
  targetNamespace="http://store"
  name="store">
  
 <component name="Catalog">
  <implementation.java class="services.store.FruitsCatalogImpl"/> 
  <property name="currencyCode">USD</property>
  <service name="Catalog">
   <tuscany:binding.rest uri="http://localhost:8085/Catalog">
                  <tuscany:wireFormat.json />
       <tuscany:operationSelector.jaxrs />
              </tuscany:binding.rest>
     </service>
  <reference name="currencyConverter" target="CurrencyConverter"/> 
 </component> 
    
 <component name="CurrencyConverter">
  <implementation.java class="services.store.CurrencyConverterImpl"/>
 </component>

</composite>

Below is the Catalog Interface utilizing JAX-RS standard annotations to map HTTP operations to business operations.


package services.store;

import javax.ws.rs.DELETE;
import javax.ws.rs.GET;
import javax.ws.rs.POST;
import javax.ws.rs.PUT;
import javax.ws.rs.Path;
import javax.ws.rs.PathParam;

import org.oasisopen.sca.annotation.Remotable;


@Remotable
public interface Catalog {
    
    @GET
    Item[] getAll();
    
    @GET
    @Path("{id}")
    Item getItemById(@PathParam("id") String itemId);
    
    @POST
    void addItem(Item item);
    
    @PUT
    void updateItem(Item item);
    
    @DELETE
    @Path("{id}")
    void deleteItem(@PathParam("id") String itemId);
}

Below is the Fuit catalog implementation


@Scope("COMPOSITE")
public class FruitsCatalogImpl implements Catalog {
    
    @Property
    public String currencyCode = "USD";
    
    @Reference
    public CurrencyConverter currencyConverter;
    
    private Map catalog = new HashMap();

    @Init
    public void init() {
        String currencySymbol = currencyConverter.getCurrencySymbol(currencyCode);
        catalog.put("Apple", new Item("Apple",  currencySymbol + currencyConverter.getConversion("USD", currencyCode, 2.99)));
        catalog.put("Orange", new Item("Orange", currencySymbol + currencyConverter.getConversion("USD", currencyCode, 3.55)));
        catalog.put("Pear", new Item("Pear", currencySymbol + currencyConverter.getConversion("USD", currencyCode, 1.55)));
    }

    public Item[] getAll() {
        Item[] catalogArray = new Item[catalog.size()];
        catalog.values().toArray(catalogArray);
        return catalogArray;
    }
    
    public Item getItemById(String itemId) {
        return catalog.get(itemId);
    }
    
    public void addItem(Item item) {
        catalog.put(item.getName(),item);
    }
    
    public void updateItem(Item item) {
        if(catalog.get(item.getName()) != null) {
            catalog.put(item.getName(), item);
        }
    }
    
    public void deleteItem(String itemId) {
        if(catalog.get(itemId) != null) {
            catalog.remove(itemId);
        }        
    }
}

Call for Participation: Technical Talks -- ApacheCon North America 2010

2010-04-28T10:51:00.000-07:00

ApacheCon North America 2010
1-5 November 2010 -- Westin Peachtree in Atlanta

Technical Tracks: Call For Participation
All submissions must be received by Friday, 28 May 2010 at midnight Pacific Time.
The official conference, trainings, and expo of The Apache Software Foundation (ASF) returns to Atlanta this November, with dozens of technical, business, and community-focused sessions at the beginner, intermediate, and advanced levels.

Over the past decade, the ASF has gone from strength to strength, developing and shepherding nearly 150 Top-Level Projects and new initiatives in the Apache Incubator and Labs. This year's ApacheCon celebrates how Apache technologies have sparked creativity, challenged processes, streamlined development, improved collaboration, launched businesses, bolstered economies, and improved lives.

We are proud of our achievements and recognize that the global Apache community --both developers and users-- are responsible for the success and popularity of our products.

The ApacheCon Planning Team are soliciting 50-minute technical presentations for the next conference, which will focus on the theme “Servers, the Cloud, and Innovation”.

We are particularly interested in highly-relevant, professionally-directed presentations that demonstrate specific probrlems and real-world solutions. Part of the technical program has already been planned; we welcome proposals based on the following Apache Projects and related technical areas:

- Cassandra/NoSQL
- Content Technologies
- (Java) Enterprise Development
- Felix/OSGi
- Geronimo
- Hadoop + friends/Cloud Computing
- Lucene, Mahout + friends/Search
- Tomcat
- Tuscany
Submissions are open to anyone with relevant expertise: ASF affiliation is not required to present at, attend, or otherwise participate in ApacheCon.

Please keep in mind that whilst we encourage submissions that the highlight the use of specific Apache solutions, we are unable to accept marketing/commercially-oriented presentations.

Other proposals, such as panels, or those longer than 50 minutes in duration have been considered in the past. You are welcome to submit an alternate presentation, however, such sessions are accepted under exceptional circumstances. Please be as descriptive as possible, including names/bios of proposed panelists and any related details.

All accepted speakers (not co-presenters) qualify for general conference admission and a minimum of two nights lodging at the conference hotel. Additional hotel nights and travel assistance are possible, depending on the number of presentations given and type of assistance needed.

To submit a presentation proposal, please send an email to submissions AT apachecon DOT com containing the following information in plaintext (no attachments, please):

1. Your full name, title, and organization

2. Contact information, including your address

3. The name of your proposed session (keep your title simple and relevant to the topic)

4. The technical category of the intended presentation (Cassandra/NoSQL; Content Technologies; (Java) Enterprise Development; Felix/OSGi; Geronimo; Hadoop + friends/Cloud Computing; Lucene, Mahout + friends/Search; Tomcat; or Tuscany)

5. The classification for each presentation (Servers, Cloud, or Innovation) – some presentations may have more than one theme (e.g., a next-generation server can be classified both as "Servers" and "Innovation"

6. The intended audience level (beginner, intermediate, advanced)

7. A 75-200 word overview of your presentation

8. A 100-200-word speaker bio that includes prior conference speaking or related experience

9. Feedback or references (with contact information) on presentations given within the last three years

To be considered, proposals must be received by Friday, 28 May 2010 at midnight Pacific Time. Please email any questions regarding proposal submissions to cfp AT apachecon DOT com.

Technical Tracks Key Dates

23 April 2010: Call For Participation Open
28 May 2010: Call For Participation Closes
11 June 2010: Speaker Acceptance/Rejection Notification
1-5 November 2010: ApacheCon NA 2010
We look forward to seeing you in Atlanta!

For the ApacheCon Planning team,
Sally Khudairi, Program Lead

The glory of REST and Hypermedia...

2010-04-15T12:52:00.000-07:00

Just stumbled upon this interesting article on how to conquer the glory of REST, and decided to share it here. One interesting thing is how Hypermedia is kind of the last step towards the glory... and this might be a good addition to services based on the current REST support in Tuscany.

Recently I've been reading drafts of Rest In Practice: a book that a couple of my colleagues have been working on. Their aim is to explain how to use Restful web services to handle many of the integration problems that enterprises face. At the heart of the book is the notion that the web is an existence proof of a massively scalable distributed system that works really well, and we can take ideas from that to build integrated systems more easily.

Read the full article here....

ApacheCon NA 2010 Business/Community Track Call For Participation

2010-03-21T13:22:00.000-07:00

ApacheCon North America 2010
Business/Community Track Call For Participation

All submissions must be received by Friday, 30 April 2010 at midnight Pacific Time.

The official conference, trainings, and expo of The Apache Software Foundation (ASF) will return to Atlanta this November, with dozens of sessions on Servers, Cloud Computing, Search, NoSQL, Incubating projects, innovations, emerging technologies, and more. ApacheCon's technical tracks are currently being planned by their respective Project Management Committees and will be announced in the upcoming weeks.

Over the past five years, the ApacheCon Business/Community Track brought some of the most compelling non-technical topics in Open Source, bridging user, developer, and deployment issues as they relate to customer and community success.

We are soliciting 50-minute presentations for the Business/Community Track at the next conference, 1-5 November 2010, at the Westin Peachtree in Atlanta.

The ASF's meritocratic process known as "The Apache Way", is widely credited for the success of many leading Open Source projects and communities. We are particularly interested in presentations that demonstrate real-world examples that address The Apache Way and its impact on the following topics:

- The Business of Open Source (policies, governance, ecosystem)
- Adoption Success Stories (enterprise/business, military/government, non-profit/academic/research)
- Business Model Strategies (evolving landscape, transforming changes, emerging trends)
- Apache in the Enterprise (motivations, operations, markets, interoperability)
- Open Source In the House (tips/tricks/tools that improve internal processes, productivity, collaboration)
- Open Development and Distributed Computing
- Educating and Evangelizing
- Open Source Licenses and Legal Issues (roadmaps, hybrid environments, compatibility, etc.)
- Meritocracy Model and Community Building
- Mentoring Projects, Users, and Communities
- Fostering Emerging Group Participation (students, women, multi-national, etc.)

Other proposals on topics of interest that showcase “how we did it” are also welcome. Submissions are open to anyone with relevant expertise: ASF affiliation is not required to present at, attend, or otherwise participate in ApacheCon.

Please keep in mind that whilst we are encourage submissions that the highlight the use of specific Apache solutions, we are unable to accept marketing/commercially-oriented presentations.

All accepted speakers (not co-presenters) qualify for general conference admission and a minimum of two nights lodging at the conference hotel. Additional hotel nights and travel assistance are possible, depending on the number of presentations given and type of assistance needed.

To submit a 50-minute presentation proposal, please send an email to bizcom AT apachecon DOT com containing the following information in plaintext (no attachments, please):

1. Your full name, title, and organization

2. Contact information, including your address

3. The name of your proposed session (keep your title simple and relevant to the topic)

4. The category of the intended presentation (Business or Community)

5. A 75-200 word overview of your presentation

6. A 100-200-word speaker bio that includes prior conference speaking or related experience

7. Feedback or references (with contact information) on presentations given within the last three years

To be considered, proposals must be received by Friday, 30 April 2010 at midnight Pacific Time. Please email any questions regarding proposal submissions to bizcom AT apachecon DOT com.

Business/Community Track Key Dates

20 March 2010: Call For Participation Open
30 April 2010: Call For Participation Closes
17 May 2010: Speaker Acceptance/Rejection Notification
1-5 November 2010: ApacheCon NA 2010

We look forward to seeing you in Atlanta!

Business/Community Track Chairs
Sally Khudairi, Vice President, ASF Marketing & Publicity
Luciano Resende, Apache Community Development Committee

Google has officially announced that GSoC 2010 is ON !!!

2010-01-26T17:23:00.000-08:00

Leslie Hawthorn, Google Open Source Program Manager has just announced that GSoC 2010 is On !!!

Many of you were wondering if Google Summer of Code 2010 is on for 2010 and the answer is yes! We will begin accepting application from would-be mentoring organizations beginning March 8th at approximately 19:00 UTC, with applications closing on March 12th at 23:00 UTC. Students can apply between 19:00 UTC on March 29th to 19:00 UTC on April 9th.

Articles: SCA Articles from IBM WebSphere Application Server Feature Pack for SCA

2010-01-21T11:50:00.000-08:00

Community Development at The Apache Software Foundation (Part II)

2010-01-14T08:04:00.000-08:00

More coverage of our Community Development effort at Apache.

In an effort to centralize developer resources and help newcomers to open source, the Apache Software Foundation recently launched the Community Developer project. So far, the project includes plans for a mentoring program, a "Newbie FAQ", and resources for educators. To find out how the project started and where it's going, DZone conducted an exclusive interview with Bertrand Delacretaz, an Apache member who has been with the project since the beginning. He says some of the major goals for the project include mentoring for student developers and an entry point to the foundation at-large.

If you are interested in learning about open source, or have some experience that you want to share by mentoring others, please come join us by subscribing to our mailing list.

Community Development at The Apache Software Foundation

2010-01-06T09:34:00.000-08:00

Some folks at Apache are actively working on a mentoring project similar to GSoC aiming on helping students and the community in general to get started with open source. Below is a post with some pointers about the program.

The Apache Software Foundation have launched a new Community Development project site that aims to help newcomers integrate into the ASF community. The site is still in the early stages, but currently offers an introduction to the ASF mentoring programme and formal mentoring programme, and a newbie FAQ. Newcomers are also invited to subscribe to the ASF community mailing list.

If you are interested in learning about open source, or have some experience that you want to share by mentoring others, please come join us by subscribing to our mailing list.

Google App Engine SDK 1.2.8 Released and they are finally supporting JAXB

2009-12-03T22:00:00.000-08:00

Google has announced the new App Engine SDK 1.2.8 and they are finally providing support for JAXB.

The App Engine team has been hard at work tackling our the issues on our tracker, tweaking APIs and closing bugs. In addition to a ton of bug fixes, 1.2.8 also includes:

Enhanced Admin Console - Users will notice new tools for managing tasks and queues created with the Task Queue API, and more visibility into index processing.

Improved Java Compatibility - This release adds support for new filter operators and inheritance to JPA and JDO as well as support for JAXB, the single most requested feature for the Java SDK.

...

Apache PhotArk - Improved documentation and new website is now live !!!

2009-11-29T21:29:00.000-08:00

Apache PhotArk will be a complete open source photo gallery application including a content repository for the images, a display piece, an access control layer, and upload capabilities. The idea is to have a rigid design for the content repository with a very flexible display piece. The images in the content repository will be protected with granular access control.

The new PhotArk website layout is live, and it has improved documentation with a improved developer guide and a new architecture guide.

Apache PhotArk 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 the Apache PhotArk project, visit the website at:

http://incubator.apache.org/photark/

Thank you for your interest in Apache PhotArk!

The Apache PhotArk Team.

Tuscany SVN structure has changed...

2009-11-20T16:18:00.000-08:00

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

2009-11-06T13:56:00.000-08:00

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

Subversion is being proposed as an Apache Incubator project

2009-11-04T13:47:00.000-08:00

The CollabNet-sponsored Subversion project and The Apache Software Foundation (ASF) announced today that the award-winning Open Source project has formally submitted itself to the Apache Incubator in order to become part of the Foundation's efforts.

Read the Press Release....

ApacheCon 2009 Session : SCA, Java EE, Spring, Web 2.0 and Cloud Come Together - Service assembly with Apache Tuscany SCA

2009-11-04T13:38:00.000-08:00

ApacheCon US 2009 has started and I'm done with my first Apache Tuscany session.

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

Slides are now available

Tuscany cloud tutorial source code is available in Tuscany SVN at sca-cloud-tutorial sandbox.

The application integration sample (a.k.a Travel Sample) is available in Tuscany SVN at travel-sample sandbox.

Distributed online store scenario running on multiple cloud environments.

2009-10-30T11:48:00.000-07:00

In my previous post, I described A variant of the Store scenario running on Google AppEngine. I have expanded the scenario to incorporate other catalogs hosted in different cloud environment, and have added a vegetables catalog hosted in the IBM cloud.

One of the problems that raises when you start thinking on multiple cloud environments, is that the is no current Cloud Standard, and trying to consume cloud infrastructure services will make your application dependent on a given cloud environment. To solve this problem, we have now started an abstraction layer for these cloud infrastructure services, similar to the idea proposed by simpleCloud.org. We have defined a userService which abstracts user related services, and a DocumentStore which is used to handle data store services and is based on the Tuscany Collection interface that easily maps to REST. We are still maturing this cloud api layer, and the current store scenario uses the userServices implementation based on Google AppEngine UserServices to provide authentication support for the application, as well as to provide individual shoppingCarts per user.

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 distributed online store scenario is available in the sca cloud tutorial sandbox.

Tuscany Sessions at ApacheCon US 2009

2009-10-26T13:46:00.000-07:00

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.

New IBM products featuring SCA

2009-10-24T21:37:00.000-07:00

IBM boosts business agility in WebSphere middleware upgrade

A slew of products are offered in the WebSphere Version 7 upgrade, with a focus on BPM, SOA, and business strategy layers for IT

...

The WebSphere BPM suite is being fitted with a native container as part of the platform's SCA (Service Component Architecture) capabilities. With this container, users can take the definition of a business process and turn it into an executing system in one click, Hayman said. SCA, Shimmin said, enables IBM to make its software more modular.

Read full article...

Google AppEngine SDK and Maven

2009-10-23T19:45:00.000-07:00

While building some cloud applications scenario with Tuscany, I needed a way to have the Google AppEngine dependencies working together with my Maven build Environment. As the Google guys don't publish the Google SDK in Maven, I had to consider different approaches such as manually installing the dependencies in my local maven repo as suggested by Shalin. But I wanted something more automated and less intrusive to the application developer, and I just decided to create a ant script that automates the download of the necessary dependencies, and add them to your local maven repo just as if the SDK were available from a public maven repo. See below how to use the script and how to add the dependencies into your application.

The ant script to install Google AppEngine SDK (build-appengine.xml):


<project name="AppEngineSDKInstaller">
    <property name="appengine.version" value="1.2.6"/>
 <property name="appengine.distribution.location" value="http://googleappengine.googlecode.com/files/appengine-java-sdk-${appengine.version}.zip" />
    <property name="unpack.location" value="${basedir}/target/appengine-java-sdk-${appengine.version}"/>
 
 <property name="appengine.tools.api" value="${basedir}/target/appengine-java-sdk-${appengine.version}/lib/appengine-tools-api.jar"/>
 <property name="appengine.api" value="${basedir}/target/appengine-java-sdk-${appengine.version}/lib/impl/appengine-api.jar"/>
 <property name="appengine.local.runtime.shared" value="${basedir}/target/appengine-java-sdk-${appengine.version}/lib/shared/appengine-local-runtime-shared.jar"/>

    <target name="check-installed">
        <condition property="already.installed" >
            <available file="${localRepository}/com/google/appengine-java-sdk/${appengine.version}/appengine-java-sdk-${appengine.version}.zip"/>
        </condition>
        <condition property="maven.suffix" value="">
            <os family="unix"/>
        </condition>
        <condition property="maven.suffix" value=".bat">
            <os family="windows"/>
        </condition>
    </target>
 

    <target name="check-unpacked">
        <condition property="already.unpacked" >
            <available file="${unpack.location}"/>
        </condition>
    </target>

    <target name="install" depends="check-installed" unless="already.installed">
        <mkdir dir="${basedir}/target/appengine-download/"/>
        <get src="${appengine.distribution.location}"
            dest="${basedir}/target/appengine-download/appengine-java-sdk-${appengine.version}.zip"
            verbose="true"
            usetimestamp="true"/>
        <exec executable="mvn${maven.suffix}" dir="${basedir}" failonerror="false">
            <arg line="install:install-file -DgroupId=com.google  -DartifactId=appengine-java-sdk -Dversion=${appengine.version} -Dpackaging=zip -DgeneratePom=true -Dfile=${basedir}/target/appengine-download/appengine-java-sdk-${appengine.version}.zip"/>
        </exec>
     
     <antcall target="unpack-appengine-sdk"/>

     <exec executable="mvn${maven.suffix}" dir="${basedir}" failonerror="false">
            <arg line="install:install-file -DgroupId=com.google.appengine  -DartifactId=appengine-tools -Dversion=${appengine.version} -Dpackaging=jar -DgeneratePom=true -Dfile=${appengine.tools.api}"/>
        </exec>

     <exec executable="mvn${maven.suffix}" dir="${basedir}" failonerror="false">
            <arg line="install:install-file -DgroupId=com.google.appengine  -DartifactId=appengine-api -Dversion=${appengine.version} -Dpackaging=jar -DgeneratePom=true -Dfile=${appengine.api}"/>
        </exec>

     <exec executable="mvn${maven.suffix}" dir="${basedir}" failonerror="false">
            <arg line="install:install-file -DgroupId=com.google.appengine  -DartifactId=appengine-local-runtime-shared -Dversion=${appengine.version} -Dpackaging=jar -DgeneratePom=true -Dfile=${appengine.local.runtime.shared}"/>
        </exec>

     <exec executable="mvn${maven.suffix}" dir="${basedir}" failonerror="false">
            <arg line="install:install-file -DgroupId=com.google.appengine  -DartifactId=appengine-tools -Dversion=${appengine.version} -Dpackaging=jar -DgeneratePom=true -Dfile=${appengine.tools.api}"/>
        </exec>

    </target>

    <target name="unpack-appengine-sdk" depends="check-installed, check-unpacked" unless="already.unpacked">
        <fail message="AppEngine SDK zip file not installed in local repository: ${localRepository}" unless="already.installed"/>
        <mkdir dir="${basedir}/target/appengine-unpack-temp/"/>
        <unzip src="${localRepository}/com/google/appengine-java-sdk/${appengine.version}/appengine-java-sdk-${appengine.version}.zip"
               dest="${basedir}/target/appengine-unpack-temp/"
               overwrite="false">
        </unzip>
        <move todir="${unpack.location}">
         <fileset dir="${basedir}/target/appengine-unpack-temp/appengine-java-sdk-${appengine.version}"/>
        </move>
        <delete dir="${basedir}/target/appengine-unpack-temp/"/>
    </target>
 

    <target name="clean-appengine-files">
        <delete dir="${unpack.location}"/>
    </target>
</project>

Configuring your application pom to run this script:


<build>
  <plugins>
   <plugin>
    <groupId>org.apache.felix</groupId>
    <artifactId>maven-bundle-plugin</artifactId>

    <configuration>
     <instructions>
      <Bundle-Version>2.0.0</Bundle-Version>
      <Bundle-SymbolicName>org.apache.tuscany.sca.cloud.api.google</Bundle-SymbolicName>
      <Bundle-Description>${pom.name}</Bundle-Description>
      <Export-Package>org.apache.tuscany.sca.cloud*</Export-Package>
     </instructions>
    </configuration>
   </plugin>


            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-eclipse-plugin</artifactId>
                <configuration>
                    <projectnatures>
                        <projectnature>org.eclipse.jdt.core.javanature</projectnature>
                        <projectnature>com.google.appengine.eclipse.core.gaeNature</projectnature>
                        <projectnature>com.google.gdt.eclipse.core.webAppNature</projectnature>
                    </projectnatures>
                    <buildcommands>
                        <buildCommand>org.eclipse.jdt.core.javabuilder</buildCommand>
                        <buildCommand>com.google.appengine.eclipse.core.enhancerbuilder</buildCommand>
                        <buildCommand>com.google.appengine.eclipse.core.projectValidator> </buildCommand>
                        <buildCommand>com.google.gdt.eclipse.core.webAppProjectValidator> </buildCommand>
                    </buildcommands>
                    <classpathContainers>
                        <classpathContainer>org.eclipse.jdt.launching.JRE_CONTAINER</classpathContainer>
                        <classpathContainer>com.google.appengine.eclipse.core.GAE_CONTAINER</classpathContainer>
                    </classpathContainers>
                </configuration>
            </plugin>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-antrun-plugin</artifactId>
                <!-- version>1.1</version --> 
       <dependencies>
           <dependency>
            <groupId>ant</groupId>
            <artifactId>ant-trax</artifactId>
            <version>1.6.5</version>
           </dependency>
       </dependencies>                    
                <executions>
                    <execution> 
                        <id>install-appengine</id>                       
                        <phase>validate</phase>
                        <goals>
                            <goal>run</goal>
                        </goals>
                        <configuration>
                            <tasks>
                                <ant antfile="./build-appengine.xml" target="install">
                                    <property name="localRepository" value="${settings.localRepository}"/>
                                </ant>
                            </tasks>
                        </configuration>
                    </execution>
                    <execution> 
                        <id>clean-appengine-files</id>                       
                        <phase>clean</phase>
                        <goals>
                            <goal>run</goal>
                        </goals>
                        <configuration>
                            <tasks>
                                <ant antfile="./build-appengine.xml" target="clean-appengine-files">
                                    <property name="localRepository" value="${settings.localRepository}"/>
                                </ant>
                            </tasks>
                        </configuration>
                    </execution>
                </executions>
            </plugin> 

        </plugins>     
 </build>

Adding AppEngine SDK dependencies to your application pom:


 <dependencies>
  <dependency>
   <groupId>com.google.appengine</groupId>
   <artifactId>appengine-tools</artifactId>
   <version>1.2.6</version>
   <scope>provided</scope>
  </dependency>  

  <dependency>
   <groupId>com.google.appengine</groupId>
   <artifactId>appengine-api</artifactId>
   <version>1.2.6</version>
   <scope>provided</scope>
  </dependency>  

  <dependency>
   <groupId>com.google.appengine</groupId>
   <artifactId>appengine-local-runtime-shared</artifactId>
   <version>1.2.6</version>
   <scope>provided</scope>
  </dependency>  
 </dependencies>

Tuscany Java SCA 1.5.1 Released

2009-10-08T08:00:00.000-07:00

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

2009-10-06T21:28:00.000-07:00

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 !!!

2009-10-05T16:27:00.000-07:00

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.

Rio de Janeiro to become the first South American city to host the Olympic Games

2009-10-03T11:05:00.001-07:00

Thousands of people celebrated Friday on crowded Copacabana beach as the announcement that Brazil had been chosen as the 2016 Olympics host played live over huge screens erected above the sand.

Read full story

World Cup 2014, Olympics 2016, Now I just need to beg for more vacation time!!!

Apache PhotArk M1-incubating released

2009-09-28T03:15:00.000-07:00

The Apache PhotArk team is pleased to announce the release of Apache PhotArk M1-incubating.

Apache PhotArk will be a complete open source photo gallery application including a content repository for the images, a display piece, an access control layer, and upload capabilities. The idea is to have a rigid design for the content repository with a very flexible display piece. The images in the content repository will be protected with granular access control.

PhotArk gallery currently allows you define a set of albums hosted locally, and also allows you to aggregate external albums exposed as feeds (e.g from Flickr or Picassa web) and provides a default web UI for album navigation.

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

http://incubator.apache.org/photark/downloads.html

Apache PhotArk 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 PhotArk visit the website at:

http://incubator.apache.org/photark/

Thank you for your interest in Apache PhotArk!

The Apache PhotArk Team.

Free Event: BarCampApache Oakland

2009-09-27T16:58:00.000-07:00

The two days prior to ApacheCon (2-3 Novemeber) will see the hosting of BarCampApache Oakland. This is entirely free even if not attending the conference.

Please visit the BarCamApache for more information. Registration is available at BarCampApacheAttendees.

Remember this is an ideal opportunity to seek out people of like mind. At a BarCamp you can talk about anything you think people will be interested in - your favourite project, how to enjoy yourself in Oakland, survival tips for ones first month on an ASF list, Why you love your job, why you hate your job etc. etc. there will be plenty of space to break off and continue discussion with people of like mind.

Perspectivas Speaker Series: Leadership and Vision by Jerry Porras

2009-09-23T19:09:00.000-07:00

This is a very nice talk from Jerry Porras as a Google Tech Talk. Hope you guys enjoy and get inspired.

Getting up and running with "Eucalyptus Public Cloud"

2009-09-22T18:53:00.000-07:00

I have been looking recently on what's available as Cloud infrastructure, particularly the open source ones. On this post, I'll describe a little about the "Eucalyptus Public Cloud" and how you can get a test instance configured and running.

Eucalyptus cloud originated in the Computer Science department at the University of California, Santa Barbara as a research project and is a open-source software infrastructure for implementing "cloud computing" on clusters. from the University The current interface to Eucalyptus is compatible with Amazon's EC2, S3, and EBS interfaces, but the infrastructure is designed to support multiple client-side interfaces

Getting Started

The Open Eucalyptus wiki is a good start point, it will direct you to apply for an account, activate it and install Amazon's client tools.

Installing and Configuring the Amazon's Client Tools

Download the Amazon EC2 API Tools : ec2-api-tools-1.3-30349.zip
Follow the configuration instructions
- Environment Configuration
- export EC2_HOME=
- export PATH=$PATH:$EC2_HOME/bin
- Configure Certificates
- Download certificates from : https://mayhem9.cs.ucsb.edu:8443/#credentials
- export EC2_PRIVATE_KEY=~/.ec2/pk-HKZYKTAIG2ECMXYIBH3HXV4ZBZQ55CLO.pem
- export EC2_CERT=~/.ec2/cert-HKZYKTAIG2ECMXYIBH3HXV4ZBZQ55CLO.pem
- Configure the open eucalyptus env
- run the eucarc provided with your credentials

- Configure Key Pair for ssh
- ec2-add-keypair lresende > lresende.private
- ec2-describe-keypairs

- Start your own virtual machine instance
- ec2-run-instances -k lresende -n 1 emi-AD9013E6
- NOTE: list of available instances, see

- Check it's up and running
- ec2-describe-instances

- Configure ssh
- ec2-authorize -P tcp -p 22 -s 0.0.0.0/0 default

- Use 'ec2-describe-instances' to find the ip associated with your running instance

- Access the instance using ssh
- ssh -i lresende.private root@

NOTE: The current version of Open Eucalyptus (v 1.5.2) requires EC2 API Tools (v 1.3-30349)

References
- http://open.eucalyptus.com/wiki/EucalyptusPublicCloud
- http://open.eucalyptus.com/wiki/EucalyptusGettingStarted_v1.5.2
- http://s3.amazonaws.com/ec2-downloads/ec2-api-tools-1.3-30349.zip
- http://developer.amazonwebservices.com/connect/entry.jspa?externalID=351&categoryID=88
- http://docs.amazonwebservices.com/AWSEC2/2008-02-01/GettingStartedGuide/index.html?setting-up-your-tools.html

Apache PhotArk - Live Gallery available

2009-09-09T12:39:00.000-07:00

After my last post, where I introduce the Apache PhotArk project, I started getting some comments asking if there was a live gallery available.

Now there is !!! I have deployed the PhotArk webapp from our RC4 into a "in progress demo" website, and I'll start migrating my own photos to be hosted in PhotArk gallery.

Please access the demo gallery at :

http://www.figueiredos.com:8080/photoark/

Apache PhotArk - A open source photo gallery project

2009-09-05T17:08:00.000-07:00

Apache PhotArk is currently under Incubation at the Apache Software Foundation.

Apache PhotArk has a goal to be a complete open source photo gallery application including a content repository for the images, a display piece, an access control layer, and upload capabilities. The idea is to have a rigid design for the content repository with a very flexible display piece. The images in the content repository will be protected with granular access control.

PhotArk gallery currently allows you define a set of albums hosted locally, and also allows you to aggregate external albums exposed as feeds (e.g from Flickr).

While we have our 1st milestone release under review, we are currently seeking help to enhance PhotArk to become a first class photo gallery application. Join our mailing lists, setup your development environment, and get involved.

Apache PhotArk is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Incubator PMC. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.

Workaroud for Java Bug 6354718 in SUN JDK 1.6u14 : Client connections to ORB are neither freed nor garbage collected

2009-09-03T17:40:00.000-07:00

The 6354718 Java Bug describes a bug where ORB connections are not freed up.

If a client connection to an ORB (omniORB in this case) is established from an application (i.e. a servlet) running under Tomcat (i.e. this app is running for weeks w/o being restarted) and all work with the orb is done, the connection to the orb should be released and all resources should be freed (especially the occupied port of course).

The code below is based on the suggested workaround posted as a comment to this bug but only works for JDK 1.6u13 and below...


 // only destroy this if we created the orb instance.
 if (createdOrb != null) {
    createdOrb.shutdown(false);
    createdOrb.destroy();            
            
    try {
        // This is a workaround to close the sockets for SUN ORB
        Method m = createdOrb.getClass().getMethod("getTransportManager");
        Object tm = m.invoke(createdOrb);
        m = tm.getClass().getMethod("close");
        m.invoke(tm);
        m = tm.getClass().getMethod("getAcceptors");
        Collection acceptors = (Collection) m.invoke(tm);
        for(Object a: acceptors) {
            m = a.getClass().getMethod("close");
            m.invoke(a);
        }
    } catch (Throwable e) {
        // Ignore
    }
    createdOrb = null;
}

Starting with SUN JDK 1.6u14 (see Release Notes for ORB related changes) this workaround does not work anymore. The issue is that the recet changes on ORB code now removes the acceptors from the transport manager in the destroy method, thus the suggested workaround should be modified a little as follow ((thanks for Raymond Feng who provided the new code) :


 // only destroy this if we created the orb instance.
 if (createdOrb != null) {
    createdOrb.shutdown(false);
            
    try {
        // This is a workaround to close the sockets for SUN ORB
        Method m = createdOrb.getClass().getMethod("getTransportManager");
        Object tm = m.invoke(createdOrb);
        m = tm.getClass().getMethod("close");
        m.invoke(tm);
        m = tm.getClass().getMethod("getAcceptors");
        Collection acceptors = (Collection) m.invoke(tm);
        for(Object a: acceptors) {
            m = a.getClass().getMethod("close");
            m.invoke(a);
        }
    } catch (Throwable e) {
        // Ignore
    }
    // Call destroy after close the acceptors
    // In JDK 1.6u14 or later, destroy clean up the acceptors but it doesn't close them
    createdOrb.destroy();            

    createdOrb = null;
}

Tuscany 2.0 Milestone 3 released

2009-08-03T13:59:00.001-07:00

Today we released the third milestone release of the new Tuscany 2.0 SCA runtime, this is another step towards the fully OASIS specification compatible SCA runtime that we aim to have finished later this year when the final versions of the OASIS SCA specifications are released.

This Tuscany release includes lots of updates for OASIS spec compliance, along with new 2.x support for BPEL and Spring components, and support for SCA contributions as ZIP archives which enables using contribution specific application dependencies.

One other exciting new feature in this M3 release is the new tuscany.war distribution for SCA enabling Apache Tomcat. This makes updating Tomcat to support SCA really simple - deploy the war to Tomcat, go to the Tuscany admin application, click on install, and thats it, on a restart of Tomcat it can now run SCA contributions and SCA enabled Web applications.

In subsequent Tuscany releases this Tomcat integration will be enhanced to use the improved SCA domain support being developed in the Tuscany 2.x code so that SCA domains can be easily managed and created spanning applications as well as runtime instances and clusters.

To find out more and to check out the release go to the Apache Tuscany website

Contributing to Apache Open Source Projects

2009-07-23T00:41:00.000-07:00

Check it out, Roberto's chat with Justin Erenkrantz and Sander Striker which gives you a good overview of how projects work at The Apache Software Foundation.

How things are going at the Apache Software Foundation?

Justin: We currently have over 100 different projects under the Apache “umbrella” with over 2,000 committers and ~350 members of the foundation. Each project is independently operated by what we call a “PMC”. We have about 75 different top-level projects, ~30 or so projects either under Incubation (baby ASF projects), and a bunch of “labs” which are individual projects started by the foundation members.

What if I want to bring my project under the Apache umbrella?

Sander: This is what the “Incubator” is about. In short you would send a proposal to the Incubator, and find sponsoring members for your project. The information on the link is pretty extensive and describes the process from entry to graduation.

Justin: Yes, and we’ll accept *any* project that our members want to support. And, given how diverse our 350+ members are, we’ll support pretty much anything that folks can come up with.

Continue reading ‘Contributing to Apache Open Source Projects’

Article: Communication Flexibility Using Bindings

2009-07-02T08:03:00.000-07:00

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

2009-05-31T23:04:00.000-07:00

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

2009-05-29T14:09:00.000-07:00

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

2009-05-27T13:54:00.000-07:00

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/branches/sca-java-1.x/ 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.

How to use Apache Tuscany with WebSphere 7.0.0.1 and SCA FeP

2009-03-14T00:59:00.000-07:00

If you are trying to deploy a Tuscany web application in a WebSphere 7.0.0.1 with the SCA FeP, you might have noticed that things are not going very smoothly. Below is a list of steps you need to do in order to sucessfully deploy a Tuscany web application in this WWebSphere 7.0.0.1 + SCA FeP environment.

For this post, we are going to use the sample-calculator-ws-webapp sample that is available from a Tuscany Release.

Issues with META-INF\sca-contribution.xml

Tuscany/SCA uses the META-INF\sca-contribution.xml to identify the deployable composites of a given contribution (application). The WebSphere server is failing deployment of web applications that have a META-INF\sca-contribution.xml. To workaround this issue, rename sca-contribution.xml to sca-contribution-generated.xml, which is treated the same by the Tuscany runtime, but ignored by WebSphere.

Classloader configuration issues

Now that we have successfully deployed our sample-calculator-ws-webapp, we need to modify the classloader configuration. This is necessary to allow Tuscany to find all its dependencies in the webapp itself instead of the WebSphere lib directory (as some of the Tuscany dependency JARs are newer than the ones that come with WebSphere). You will need to perform the following steps:

Open the "sample-calculator-ws-webapp" from the in the Enterprise Applications list

Click on the Class loading and update detection link

Select "Classes loaded with application class loader first"

Select "Single class loader for application"

Select OK and save

Start the application from the Enterprise Applications list

Check detailed steps on how to change the classloader configuration in this article from Jean-Sebastien Delfino.

Properly configuring WebServices ports

The last issue we need to deal is to fixup the ports used by webservice binding. By default, the Calculator.composite is configured to use port 8080. In order to this sample work, you need to modify the calculator.composite and update to the same port used by your WebSphere application server (e.g 9080)

Now you should be good to go, and ready to have your Tuscany webapp deployed in a WebSphere Applicatoin Server 7.0.0.1 with SCA FeP.

Java SCA 2.0-M1 release post at InfoQ

2009-03-04T22:54:00.000-08:00

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).

Book: Early edition of "Apache Tuscany in Action"

2009-02-23T08:00:00.000-08:00

I came across an early edition of a book called "Apache Tuscany in Action" that is being published at manning.com Publishing. This book teaches SCA through Tuscany with real usage examples. It looks like the application is being developed in Tuscany source code repository.

Google Summer of Code 2009

2009-02-20T16:00:00.000-08:00

Below is a nice video that gives you an overview of the 2009 Google Summer of Code program

Google hasn't announced the list of mentor organizations yet, but, as in past years, the Apache Software Foundation is going to enroll itself, and we have started collecting project ideas.

Apache Tuscany SCA 2.0 M1 Released

2009-02-20T08:28:00.001-08:00

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 Information Resources

2009-02-04T20:56:00.000-08:00

Apache Tuscany SCA Java 1.4 Released

2009-01-13T10:12:00.000-08:00

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

2009-01-08T18:19:00.000-08:00

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

2009-01-08T09:53:00.000-08:00

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.

Article: Experiments, Expertise and Google Summer of Code™, Leslie Hawthorn

2008-12-10T09:37:00.000-08:00

Worth reading Leslie's article about Google Summer of Code™

In this article, we examine the Google Summer of Code (GSoC) program, the world's first global initiative to introduce College and University students to free/libre open source software (F/LOSS) development. Over the past four years, the program has provided a model that allows College and University students to more deeply engage with the joys of computing. The experience of our participants stands in sharp contrast to the generalizations mentioned earlier. We will discuss the origins and evolutions of the program, as well as its structure. We will also discuss how students benefit by participating in GSoC, focusing on some select success stories. Finally, we discuss how Google views this investment in the F/LOSS community and its potential to improve the overall progression of Computer Science as a discipline.

Happy Birthday !!! Tuscany Celebrates 3rd Anniversary as Apache Project !!!

2008-12-07T10:04:00.000-08:00

On 2008-12-07 the Apache Tuscany project celebrates its 3rd anniversary as an Apache project. We are excited about our past accomplishments and enthusiastic about the future for Tuscany and SOA, and we would like you to join in our celebration. All week Apache Tuscany will be changing its logo and using special graphics for our virutal party, and you are invited to join.

We've had many important achievements, and the improvements for Apace Tuscany keep coming. In the past we saw the following important milestones:
November 2005 - SCA 0.9 specifications released by BEA, IBM, Oracle, SAP, IONA, and Sybase.
December 2005 - Apache Tuscany added as an Apache incubator project.
January 2006+ - Apache Tuscany release various milestones on the way to 1.0.
May 2006+ - Apache Tuscany presents at JavaOne, ApacheCon, SOA World, and others.
July 2006 - SCA 0.95 specifications released. OpenSOA formed. New companies join.
September 2007 - Apache Tuscany 1.0 release. First implementation of SCA version 1.0 specification.
February 2008 - Apache Tuscany 1.1 release with SCA policy support, many Web 2.0 bindings, platform integration.
April 2008 - Apache Tuscany 1.2 release with distributed SCA Domain management,
JAX-WS annotations, and new Atom binding.
June 2008 - Tuscany goes worldwide with opening of Chinese portal and discussion groups.
May 2008 - Apache Tuscany becomes and official top level Apache project.
September 2008 - Apache Tuscany release exciting video series. Hollywood takes note.
August 2008 - Apache Tuscany 1.3 release with improved Java2WSDL, performance and full security enablement.
December 2008 - Apache Tuscany 1.4 being readied for public consumption.

The people on the Apache Tuscany team are happy on this anniversary, and look forward to the future. We invite you to try our release and celebrate with us.

Article: How SOA is influencing Enterprise Applications

2008-11-14T19:11:00.000-08:00

The Brazilian magazine "Mundo Java" has devoted this issue for the Future and Tendencies of the Java platform and I have written a small article that talks about how SOA has been influencing how Java Enterprise Applications are developed. The article gives you a quick overview on the evolution of how Java Enterprise Applications are built, what are the issues with some technologies used to build these applications, and how new technologies are trying to address these issues and are seeing increasingly user adoption. The only problem is that you guys are going to have to learn Portuguese in order to be able to read it...

OSGi in the Enterprise

2008-11-12T14:39:00.000-08:00

This recent post at InfoQ entitled OSGi in the Enterprises describes how Enterprises and various open source projects are moving to OSGi to enable greater modularity and to allow the system to be decomposed into more manageable (and testable) units, where at the same time providing greater re-use of the component libraries.

It also mentions the work we have been doing in the Tuscany Project, that is described in this previous post : Felix Goes to Tuscany - Applying OSGi modularity after the fact

SOA goes Social @ SOASocial.com/

2008-11-07T07:09:00.000-08:00

SOASocial.com has recently been launched as a collaboration place for people interested in SOA. The site already have various articles recommended by the community, and is also a good place to exchange ideas with other people interested in SOA related topics.

Felix Goes to Tuscany - Applying OSGi modularity after the fact

2008-11-06T18:16:00.000-08:00

Here is the talk I gave today at ApacheCon US 2008 New Orleans. It shares the Tuscany Community's experience around applying OSGi modularity to an existing project.

Felix Goes to Tuscany - Applying OSGi modularity after the fact

Help the Tuscany Community with a 2 minute user survey

2008-11-06T16:41:00.000-08:00

Tuscany aims at addressing real SOA problems and for this reason we are conducting a survey to better learn how Tuscany is helping you with your SOA solutions or how it can further be enhanced.

This short survey is anonymous and will take 1-3 minutes.

We are interested to hear from you if you have used Tuscany or are interested to use Tuscany. Input from all types of users is important to us, from experience of running your business critical Tuscany applications in production to just experimenting with Tuscany in your spare time - all input is appreciated. Help us make Apache Tuscany even better and more useful. Thank you for your help in advance.

Click here to take the survey

ApacheCon live video streaming available; keynotes and Apache 101 are free

2008-11-04T13:36:00.001-08:00

Can't make ApacheCon this week in New Orleans? You can still watch all the keynotes, Apache 101 sessions, and system administration track in live video streams:

http://streaming.linux-magazin.de/en/program_apacheconus08.htm?ann

Keynotes and the Apache 101 lunchtime sessions are free; the full sysadmin track, including httpd performance, security, and server stack administration talks are available for a fee.

Keynotes include:
- David Recordon, Six Apart (Wednesday 09:30)
"Learning from Apache to create Open Specifications"

- Shahani Markus Weerawarana, Ph.D. (Thursday 11:30)
"Standing on the Shoulders of Giants"

- Sam Ramji, Microsoft (Friday 11:30)
"struct.new("future", :open, :microsoft)"

Reminder: New Orleans is CST or UTC/GMT -6 hours.

Advance notice: ApacheCon EU 2009 returns to Amsterdam, 23-27 March. We had a great response to our CFP and look forward to announcing the schedule in the next month.

ApacheCon live video streaming available; keynotes and Apache 101 are free

2008-11-04T13:36:00.000-08:00

Can't make ApacheCon this week in New Orleans? You can still watch all
the keynotes, Apache 101 sessions, and system administration track in
live video streams:

http://streaming.linux-magazin.de/en/program_apacheconus08.htm?ann

Keynotes and the Apache 101 lunchtime sessions are free; the full
sysadmin track, including httpd performance, security, and server stack
administration talks are available for a fee.

Keynotes include:
- David Recordon, Six Apart (Wednesday 09:30)
"Learning from Apache to create Open Specifications"

- Shahani Markus Weerawarana, Ph.D. (Thursday 11:30)
"Standing on the Shoulders of Giants"

- Sam Ramji, Microsoft (Friday 11:30)
"struct.new("future", :open, :microsoft)"

Reminder: New Orleans is CST or UTC/GMT -6 hours.

Advance notice: ApacheCon EU 2009 returns to Amsterdam, 23-27 March. We
had a great response to our CFP and look forward to announcing the
schedule in the next month.

Google Summer of Code 2008 Mentor Summit - day two

2008-10-26T21:26:00.000-07:00

Today was the second and last day of Google Summer of Code Mentor Summit.

Couple sessions trying to share organization/mentor experience from sucessful projects and some discussion on how to keep sucessful students participating and contributing to the community. Among other suggestions, below are couple ones I particularly liked and will try to adopt not only for GSoC, but with the community in general :
- Express your gratitude for the good contributions. This is the same principal fathers use with their kids, basically say "good job" to members of the community that deserve it.
- Another thing is to foster a friendship with the students, and basically known them better and learn what's the best approach to get the student really committed to the project.

Still about GSoC Summit, but changing gears a bit towards Apache Software Foundation. It was very good to see that Apache was mentioned multiple times in the good way, and it looks like Google and others have great admiration for ASF. In the other hand, was little frustrating to see couple people associating Apache to Apache HTTP, and not really to recognize Apache as an umbrella organization that have many more important and interesting projects. Maybe I was just talking with the wrong people, but if this is a general view, we might be in need of an "education campaign" to let people know more about Apache, The Apache Software Foundation.

And again, Leslie Rocks !!!
Thanks, Google, Leslie and all the mentors that made this a very single learning opportunity !!!

Google Summer of Code 2008 Mentor Summit - day one

2008-10-25T22:12:00.000-07:00

Every year after Summer of Code is over, Google hosts a summit at its headquarters in Mountain View to foster sharing of mentors experience, and also to learn first hand what could be improved for next year program.

Today was the first day for the 2008 Mentor Summit, and following the unconference idea, various group of people gather together to discuss Summer of Code and other OSS related topics.

Among other sessions I attended, one was related to "Open source quality through public review notes", and was interesting to see that some communities have very strict review process that can take more then a month, just to accept someone contribution's to its source code repository. My first reaction to this was that this kind of barrier would discourage contributions, and in my view, providing a way for these contributions to be fostered in the community would encourage new members to provide new contributions and the collaboration between different members of the community would raise the contribution to an acceptable level of quality. But I guess this might be acceptable in various large, mature and complex projects.

We also discussed about "How to avoid disappeared students". It was interesting to see various different opinions and disagreements. Among various advices for Mentors, I'll probably be following these two :
- Make sure your student understand that communication is not an option, its mandatory and is reason to failure.
- Be very clear with your student about your expectations, and I would probably advice to agree up front on what criteria will be used during student's mid-term and final evaluation.

And last, but not least....
Thanks Leslie, Summer of Code Mentor Summit rocked today !!!

Android is finally available as open source

2008-10-21T14:58:00.000-07:00

Today is a big day for Android, the Open Handset Alliance, and the open-source community. All of the work that we've poured into the mobile platform is now officially available, for free, as the Android Open Source Project.

I guess we are finally going to be able to get Tuscany apps running in Android.

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

2008-10-15T15:44:00.000-07:00

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.

Service Oriented Architecture

2008-07-25T22:02:00.000-07:00

Tuscany Web 2.0 Roadmap

2008-07-07T08:25:00.000-07:00

I have started putting together a Tuscany Web 2.0 Roadmap by pulling together issues discussed on the user/dev mailing list and also some items I'd like to see available in this space.

Come and help us implement this vision. Patches, suggestions and/or comments (on the Tuscany mailing list) are welcome.

Thanks
Luciano Resende
Apache Tuscany PMC

Red Hat/JBoss & Apache Tuscany

2008-06-06T09:28:00.000-07:00

Mark Little has posted about Red Hat/JBoss intentions to join the Tuscany community.

Hi, I just wanted to let people know officially that people from Red Hat/JBoss will be getting involved with Tuscany over the coming months as we look at the best way in which to provide SCA support for our SOA Platform users. We're very excited about helping on Tuscany and complimenting the work we're doing at OASIS.

Mark.

----
Mark Little

This is very exciting news for Tuscany and a great addition to the Community.

Welcome !!!

ApacheCon 2008 - Building composite applications with SCA and Apache Tuscany

2008-05-27T12:51:00.001-07:00

The session I proposed for ApacheCon 2008, entitled 'Building composite applications with SCA and Apache Tuscany' was accepted. It will be great to talk about our recently Graduated Tuscany project, and hopefully meet some of the Apache community in person.

See you guys in New Orleans.

Apache Tuscany graduated as a Top Level Apache Project !!!

2008-05-21T22:21:00.000-07:00

Thanks everybody that helped during the "Incubation Journey" !!!
Today, May 21st, Tuscany graduated as a Top Level Apache Project.

The fun is just beginning!!!!
Let's keep up the good work !!!

Matthieu wrote:

"Special order 7B, Establish the Apache Tuscany Project, was approved by
Unanimous Vote of the directors present."

Congratulations guys!

Matthieu

Getting Started with Apache Tuscany & SCA

2008-05-18T03:15:00.000-07:00

People usually ask me how to get involved in Tuscany, and having in mind these new community members and all the GSoC students, I have created a "Tuscany Dashboard" that tries to centralize in one place most of the necessary information, documentation, guides and links to help you get started with Tuscany.

Aslo, the new Tuscany Eclipse plugin, that was first shipped with Tuscany SCA 1.2 release, improves the user experience for developers building SCA applications. It integrates Tuscany with Eclipse to help you add the Tuscany runtime to your project; edit composites by providing code assist, and to run composites directly from your development environment.

Below are two articles that utilize the new Tuscany Eclipse Plugin and give you step by step guidance on building Webservices and Web 2.0 applications using Tuscany and SCA.

First Steps - Building your first web services using Tuscany
This is a quick guide that go trough the steps of exposing your pojo component as web services.

Getting Started with Tuscany using the Tuscany Eclipse plugin
This is a quick getting started guide that go trough the steps of building the store scenario using the Tuscany Eclipse plugin.

JavaOne 2008 : Tuscany and SCA coverage, and the Brazilian community off course...

2008-05-15T08:00:00.000-07:00

It was very good to see a lot of SOA and SCA coverage at JavaOne 2008, there was at least couple sessions about these topics each day, and several were mentioning Apache Tuscany.

Also, couple good feedback worth quoting from the blogsphere :

Michael Meehan wrote:

JavaOne report: Apache Tuscany, can SOA be this easy?

In front of a packed room of a few hundred developers at the 2008 JavaOne conference yesterday, IBM’s Jean-Sebastien Delfino gave a presentation of the Apache Tuscany project, an open source implementation of the Service Component Architecture (SCA) standard. SCA is designed to facilitate a standard method of constructing, assembling and developing composite services and the Tuscany implementation (currently in version 1.2) looks to be ridiculously easy to use.

One of the mantras in the SOA space is that it’s hard to do. Sure enough, enterprise architecture and end-to-end governance come with a high degree of difficulty, but Tuscany seemingly has made it a snap to stitch together a composite, Web-based service. According to Delfino, the idea is to abstract away the plumbing details using HTML-style annotations and map out the business logic of the service.

Jeff Anderson wrote:

The Highlights of SCA at JavaWorld 2008

Tuscany is a great open source implementation of SCA, with real-world production implementations
Jean-Sebastien Delfino and Mario Antollini gave a incredible presentation on Tuscany my favorite open source implementation of SCA. The highlight of the presentation (IMHO) was when Jean-Sebastien showed had easily extend the SCA specification to include mashups/Web 2.0 component creation. My opinion this is one of the highest values of SCA, a truly comprehensive component model that spans technologies, from simple AJAX/ATOM components to more complex WSDL/SOAP style services. Brilliant.
This session really showed how easy it was to make services, or components of any nature using SCA

As for the Brazilian community, they showed up again !!! We even had representatives from the Brazilian Government discussing the engagement of the Brazilian government in consuming and producing open source software, see panel abstract below :

PAN-7063: Free and Open-Source Software (FOSS): Use and Production by the Brazilian Government

The Brazilian government has been a pioneer in the use and production of free and open-source software (FOSS). This initiative is best represented by the Brazilian Public Software Portal (BPSP), a national web site that makes available the free and open-source software produced by the government and offers several services for the local FOSS community. This presentation by the government officials who are implementing this large initiative shows how the adoption of free software, such as Java™ technology-based applications and much more, was crucial to making not only the use but especially the development of new software in the government possible. The session also shows the results of the initiatives, presenting some of the amazing software solutions now available to users worldwide, and discusses some of the next steps planned by the Brazilian government.

And below, couple Brazilian dudes posing for pictures...

InfoQ post about Tuscany SCA 1.2 Release

2008-05-14T17:40:00.000-07:00

Interested in learning a little more about what's new in Tuscany and SCA 1.2 release ?
The following InfoQ article/interview gives you some interesting insights on some of the new features and possible directions for future releases. See a little bit below:

InfoQ: Among all the features that this release has introduce which ones do you consider most important?

LR: SCA is about building distributed composite applications, and the new SCA distributed domain support with an SCA Domain Manager application allows you to build and deploy your solution into multiple SCA Nodes. These nodes can run on different platforms and runtimes (e.g Geronimo, Tomcat, Jetty, etc) or just plain J2SE.

With OSGI support, users can now run Tuscany and SCA in a OSGI Runtime.

The new Tuscany Eclipse plugin improves the user experience for developers building SCA applications. It integrates Tuscany with Eclipse to help you add the Tuscany runtime to your project; edit composites by providing code assist, and to run composites directly from your development environment.

To download Tuscany SCA 1.2, please go to the Tuscany download page.

Apache Tuscany SCA Java 1.2 released

2008-04-27T20:00:00.000-07:00

The Apache Tuscany team are delighted to announce the 1.2 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.2 release adds a number of features including:
* An improved SCA distributed domain support with an SCA Domain Manager application
* Support for running Tuscany in a OSGI runtime using Apache Felix
* Support for JAXWS annotations
* improved and simplified JMS binding
* Improved support for SCA Policies and a new Policy provider SPI
* Support for 'native' Groovy component implementation classes
* Atom binding now using Apache Abdera
* A new Eclipse plugin providing a Tuscany runtime Library and Tuscany launcher in Eclipse environment.

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

To find out more about SCA, follow the link to OASIS Open CSA

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, please visit the Apache Tuscany website.

Thank you for your interest in Apache Tuscany!

The Apache Tuscany Team.

---

Tuscany is an effort undergoing incubation at the Apache Software Foundation (ASF), sponsored by the Apache Web services PMC. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that
the project has yet to be fully endorsed by the ASF.

Automating Websphere with Maven and WebSphere Administrative Scripting tools

2008-02-15T13:36:00.000-08:00

I was recently working on automating Tuscany iTests to run on the context of a web-container, and for most of Tuscany supported web-containers we had a maven-plugin available such as cargo for Tomcat and Jetty, Geronimo had it's own one, but I could not find anything that was supporting WebSphere application server.

I had a requirement to automate the following tasks with Websphere :
- Start/Stop Server
- Deploy a given application and set specific classloader configuration required by Tuscany
- Start/Stop the application
- Undeploy the application

I started looking into some Websphere documentation, and noticed I could use some phython and decided to get this integration the following way :

Tuscany maven build -> ant scripts -> phython -> websphere admin tools

Below is the phython script that interfaces with the Websphere Admin tools and would provide the actual integration necessary for the automation. The code below should be saved in a file named "wasAdmin.py"


import sys

def getCellName():
    """Return the name of the cell connected to"""
    return AdminControl.getCell()

def getNodeName():
    """Return the name of the node connected to"""
    return AdminControl.getNode()

def startApplicationOnServer(appName,serverName):
    """Start the named application on one server"""
    print "startApplicationOnServer: Entry. appname=%s servername=%s" % ( appName,serverName )
    cellName = getCellName()
    nodeName = getNodeName()
    # Get the application manager 
    appManager = AdminControl.queryNames('cell=%s,node=%s,type=ApplicationManager,process=%s,*' %(cellName,nodeName,serverName))
    print "startApplicationOnServer: appManager=%s" % ( repr(appManager) )
    # start it
    rc = AdminControl.invoke(appManager, 'startApplication', appName)
    print "startApplicationOnServer: Exit. rc=%s" % ( repr(rc) )

def stopApplicationOnServer(appName,serverName):
    """Stop the named application on one server"""
    print "stopApplicationOnServer: Entry. appname=%s servername=%s" % ( appName,serverName )
    cellName = getCellName()
    nodeName = getNodeName()
    # Get the application manager 
    appManager = AdminControl.queryNames('cell=%s,node=%s,type=ApplicationManager,process=%s,*' %(cellName,nodeName,serverName))
    print "stopApplicationOnServer: appManager=%s" % ( repr(appManager) )
    # start it
    rc = AdminControl.invoke(appManager, 'stopApplication', appName)
    print "stopApplicationOnServer: Exit. rc=%s" % ( repr(rc) )

def installApplicationOnServer( fileName, appName, contextRoot, serverName ):
    """Install given application on the named server using given context root"""
    print "installApplicationOnServer: fileName=%s appName=%s contextRoot=%s ServerName=%s" % ( fileName, appName,contextRoot,serverName )
    AdminApp.install(fileName,'[-appname ' + appName + ' -contextroot ' + contextRoot  + ' -server ' + serverName + ' -usedefaultbindings ]')
    AdminConfig.save()
    """modify classloader model for application"""
    deploymentID = AdminConfig.getid('/Deployment:' + appName + '/')
    deploymentObject = AdminConfig.showAttribute(deploymentID, 'deployedObject')
    classldr = AdminConfig.showAttribute(deploymentObject, 'classloader')
    print AdminConfig.showall(classldr)
    AdminConfig.modify(classldr, [['mode', 'PARENT_LAST']])
    """Modify WAR class loader model"""
    AdminConfig.show(deploymentObject, 'warClassLoaderPolicy')
    AdminConfig.modify(deploymentObject, [['warClassLoaderPolicy', 'SINGLE']])
    AdminConfig.save()

def uninstallApplicationOnServer( appName ):
    """Delete the named application from the cell"""
    AdminApp.uninstall( appName )
    AdminConfig.save()



"""-----------------------------------------------------------
   Phyton script to interface with WAS Admin/Management Tools
-----------------------------------------------------------"""

if len(sys.argv) < 1:
    print "wasAdmin.py : need parameters : functionName [args]"
    sys.exit(0)
if(sys.argv[0] == 'installApplicationOnServer'):
    installApplicationOnServer(sys.argv[1], sys.argv[2], sys.argv[3], sys.argv[4])
elif(sys.argv[0] == 'startApplicationOnServer'):
    startApplicationOnServer(sys.argv[1], sys.argv[2])
elif(sys.argv[0] == 'uninstallApplicationOnServer'):
    uninstallApplicationOnServer(sys.argv[1])
else:
    print "Exiting without doing anything"

Now that we have the Phyton scripts that interfaces with the WebpShpere admin tools ready, we need a way to integrate them with the Tuscany maven build. Let's use ant scripts to do the bridge between maven and phython.



<project name="was-integration" default="main" basedir="."> 
  <property environment="env"/>
  <target name="startServer">
    <exec dir="." executable="${env.WAS_HOME}/bin/startServer.sh">
      <arg value="server1" />
    </exec>
  </target>
  <target name="stopServer">
    <exec dir="." executable="${env.WAS_HOME}/bin/stopServer.sh">
      <arg value="server1" />
    </exec>
  </target>
  <target name="installApplication">
    <exec dir="." executable="${env.WAS_HOME}/bin/wsadmin.sh">
       <arg line="-conntype SOAP -lang jython -f ${was.python.script} installApplicationOnServer ${application.war} ${application.name} ${application.contextRoot} ${application.server}" />
    </exec>
    <exec dir="." executable="${env.WAS_HOME}/bin/wsadmin.sh">
       <arg line="-conntype SOAP -lang jython -f ${was.python.script} startApplicationOnServer ${application.name} ${application.server}" />
    </exec>
   </target>

  <target name="uninstallApplication">
    <exec dir="." executable="${env.WAS_HOME}/bin/wsadmin.sh">
       <arg line="-conntype SOAP -lang jython -f ${was.python.script} uninstallApplicationOnServer ${application.name}" />
    </exec>
   </target>
</project>

Now, to integrate this to your project maven build, simply call the ant targets passing the right parameters. Below is a sample maven profile that exercise the automation.


        <profile>
            <id>websphere</id>
            <activation>
                <activeByDefault>false</activeByDefault>
            </activation>
            <properties>
                <http.port>8080</http.port>
                <http.base>http://127.0.0.1:${http.port}</http.base>
                <websphere.home>${env.WAS_HOME}</websphere.home>
            </properties>

            <build>
      <!--WAS ant integration -->
                    <plugin>
                        <groupId>org.apache.maven.plugins</groupId>
                        <artifactId>maven-antrun-plugin</artifactId>
                        <version>1.1</version>
                        <executions>
                            <!-- start Websphere server -->
                            <execution>
                                <id>start-container</id>
                                <phase>pre-integration-test</phase>
                                <goals>
                                    <goal>run</goal>
                                </goals>
                         <configuration>
                             <tasks>
                                 <ant antfile="${was.ant.script}" target="startServer"/>
                             </tasks>
                         </configuration>
                     </execution>
                            <!-- Deploy war application -->
                            <execution>
                                <id>deploy-war</id>
                                <phase>pre-integration-test</phase>
                                <goals>
                                    <goal>run</goal>
                                </goals>
                         <configuration>
                             <tasks>
                                 <ant antfile="${was.ant.script}" target="installApplication">
                                            <property name="was.python.script" value="${was.python.script}"/>
                                            <property name="application.war" value="${project.build.directory}/${project.build.finalName}.war"/>
                                            <property name="application.name" value="${project.build.finalName}.war"/>
                                            <property name="application.contextRoot" value="${project.build.finalName}"/>
                                            <property name="application.server" value="server1"/>
                                        </ant>
                             </tasks>
                         </configuration>
                            </execution>
                            <!-- unDeploy war application -->
                            <execution>
                                <id>undeploy-war</id>
                                <phase>post-integration-test</phase>
                                <goals>
                                    <goal>run</goal>
                                </goals>
                         <configuration>
                             <tasks>
                                 <ant antfile="${was.ant.script}" target="uninstallApplication">
                                            <property name="was.python.script" value="${was.python.script}"/>
                                            <property name="application.name" value="${project.build.finalName}.war"/>
                                        </ant>
                             </tasks>
                         </configuration>
                            </execution>
                            <!-- Stop Websphere server -->
                            <execution>
                                <id>stop-container</id>
                                <phase>post-integration-test</phase>
                                <goals>
                                    <goal>run</goal>
                                </goals>
                         <configuration>
                             <tasks>
                                 <ant antfile="${was.ant.script}" target="stopServer"/>
                             </tasks>
                         </configuration>
                            </execution>

                        </executions>
                    </plugin>
                </plugins>
            </build>
        </profile>

Hope this help people in the future. Also, for a working sample, see Tuscany iTests that are automated to run in the context of various web application containers, including Websphere.

Apache Tuscany SCA 1.1 Release Announced

2008-02-06T08:12:00.000-08:00

Tuscany team has just announced Java SCA 1.1 and it is now available for download on the Tuscany SCA Releases page.

The Apache Tuscany team are delighted to announce the 1.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).

The Tuscany SCA Java 1.1 release adds a number of features including a JMS binding, improved policy support and an implementation extension for representing client side Javascript applications as SCA components.

There is also a nice post at InfoQ

InfoQ spoke with Jean-Sebastien Delfino and Luciano Resende, both from IBM, who contribute to the Apache Tuscany project.
...
InfoQ: What's coming ahead ?

JS: The Tuscany community will have to decide (as we're just getting 1.1 out) but I envision progress in the following areas:

* simpler and more complete SCA policy support
* more policies (making progress with the transaction policy)
* improved end-to-end SCA contribution / deployment / distribution story
* an SCA domain administration application
* integration with Geronimo (there's a prototype in the Geronimo sandbox)
* improvements of the Web 2.0 bindings (maybe using Apache Abdera for ATOM and adding cross-domain support to the JSONRPC binding)
* optimizations of the Tuscany databinding support
* more platform integration testing (Tomcat, Geronimo etc.)

Article : Software components: Coarse-grained versus fine-grained

2007-12-06T10:06:00.000-08:00

Some of the SCA gurus at IBM have written an article around Software component granularity. Below is the article overview, and you can find the entire content here.

SOA is about providing software capabilities through interfaces called services and supporting the business concept known as service orientation, where applications are built as sets of services with service users unaware of how or where services are implemented. Beyond the interfaces—which are a key part, but not the only part of a good SOA—are software components and component models. Component models are useful for building new SOA services from the ground up, but they're also useful for creating SOA services from legacy IT assets. You can use component models to provide abstraction of legacy services and to re-engineer existing legacy assets, especially when the component model supports language neutrality.

There are many aspects to the concept of a software component. This article focuses on software components as they're used within the context of an SOA-based business service solution. In this context, you can use various software component technologies to:

* Implement business services.
* Adapt services for integration between disparate run times, languages, or interfaces.
* Provide a business-level abstraction for the composition of preexisting business services.

The software component concept can be decomposed into what this article calls coarse-grained components and fine-grained components. Unfortunately, it's not possible to define these two concepts precisely. There's a wide-ranging opinion in the industry on how to precisely delineate component granularity. For example, the OASIS SOA Reference Model (see Resources for a link) specifically rejects the notion that interface chattiness is a consideration. By contrast, the Wikipedia definitions (see Resources) primarily center on the frequency and amount of data exchanged between components. Further, the industry has adopted the concept of coupling, which is defined as the fragility exhibited in the relationship between two software components. The terms loose coupling (a small amount of fragility) and tight coupling (a large amount of fragility) are often mistakenly used as synonyms for coarse-grained and fine-grained components.

This article asserts that coupling is only one aspect of granularity, as discussed in the Component interface section, but does support the current industry thinking that, in general, loosely coupled components are coarse grained, while tightly coupled components are more likely to be fine grained. It's worth noting that while some component models focus on one form of granularity, others attempt to strike a balance between the two extremes. (See the Inventory of component technologies section for a categorization of component models based on the attributes described in this article.)

Developing an SCA application with Apache Tuscany and Eclipse

2007-11-16T20:18:00.000-08:00

This is a good post from Jean-Sebastien Delfino that describes how to use some Tuscany tools that simplify configuring Eclipse for Tuscany SCA development.

The last few months I spent a lot of time in Eclipse developing SCA samples and demos for Tuscany. I found myself tweaking my various Eclipse workspaces again and again to do the following:

- Define a Tuscany User Library containing all the Tuscany JARs to make it easier to add them to my project buildpath.

- Associate .composite files with the XML editor and register the SCA and Tuscany XML schemas to get code-assist in the editor and validation of my composite files.

- Write programs to launch Tuscany configured with my various composites... wishing that I could just right-click on the .composite and select a Run As / Tuscany...

Finally, I got tired of repeating these steps again and again and decided to put together a small tool made of two simple Eclipse plugins to package Tuscany in a Library and take care of all that configuration.

Article: Developing SOA with Apache Tuscany and SCA

2007-11-13T18:07:00.001-08:00

The brazilian magazine "Mundo Java" has devoted this issue for SOA related articles. The article "Developing SOA with Apache Tuscany and SCA", that I wrote with Paulo Trecenti, gives you an introduction and also give you hands-on experience with SCA. The only problem is that you guys are going to have to learn portuguese in order to be able to read it...

Free OASIS Webinars: Simplify Your SOA Applications Using Composite Services

2007-11-12T20:50:00.000-08:00

Learn how to design and transform your IT assets into reusable services that can be rapidly assembled to meet your changing business requirements.

Beginning 10 December, OASIS Open CSA will present four FREE webinars on the Service Component Architecture (SCA) and its role in SOA. SCA encompasses a family of royalty-free specifications that are based on the idea that business function is provided as a series of services, which can be assembled together to create solutions that serve a particular business need. SCA provides a model both for the composition of services and for the creation of service components, including the reuse of existing application function within SCA compositions.

Register for one or all four webinars and discover how to use SCA.

Series of Webinars timeframe:
3:00PM GMT, 12:00 Midnight Tokyo, 7:00AM San Francisco, 10:00AM Boston, 3:00PM London.

http://www.oasis-open.org/events/webinars/sca-2007.php.

Webinars:

SCA (Service Component Architecture) Overview (Monday, 10 December, 2007)

The SCA overview will "paint the big picture" of SCA - the aims of SCA, the various parts of SCA and how SCA relates to other technologies in the world of Service Oriented Architecture. It will cover the overall objectives of the 6 OASIS SCA TCs and their common themes.

SCA Policy Framework Tutorial (Tuesday, 11 December, 2007)

Service oriented architecture is the latest technology for building business solutions. Policy is an important aspect of service oriented systems because it often constrains how business services are meant to interact with each other. Policy also provides the means for specifying both functional and non-functional capability that must be present during assembly, deployment and execution of business services. Abstracting these capabilities into declarative requirements allows the business logic developer to create services that are not tied to a particular infrastructure or middleware provider, enabling agility, flexibility and reusability of business services.

A working knowledge of the SCA Assembly concepts is required in order to understand the basis of the examples and the features of the Policy Framework that build upon the base Assembly model. This presentation will cover the SCA Policy Framework concepts, early and late binding of policy, as well as examples of policy annotations in the Java programming language.

SCA Assembly Model (Wednesday, 12 December, 2007)

The SCA Assembly model is a vendor-, technology-, and language-neutral model for assembling composite services out of components created from a variety of technologies. In this talk, the assembly model will be described in detail and illustrated through a variety of examples and use cases.

SCA for C++, C and COBOL (Thursday, 13 December, 2007)

SCA component implementations can be written in a variety of languages. This session will provide an overview of the programming model and support for implementations written in C++, C, and COBOL. The programming interfaces and supporting annotations will be introduced. Information on the progressing standards and implementations will also be provided.

Apache Tuscany and SCA at SOAWorld 2007

2007-11-12T17:12:00.000-08:00

Raymond Feng is speaking at SOAWorld 2007 at San Francisco on November 12.

Practical SOA with Apache Tuscany

Apache Tuscany provides an open source services infrastructure for building SOA solutions. It's based on emerging Service Component Architecture (SCA) specifications. With the Tuscany implementation of SCA, application developers can easily create or reuse services in different languages (Java, C++, BPEL, XQuery or various scripting languages), assemble and deploy them in a distributed environment. It now becomes a reality that application developer can really focus on the business logic without being puzzled by the plumbing technologies. In this session, we will introduce the key aspects of SCA by real examples and demonstrate how simple, flexible and powerful the experience can be to develop SOA solutions with Tuscany.

Article : Building SOA with Tuscany SCA - A simple service-oriented infrastructure

2007-11-11T23:00:00.000-08:00

Building SOA with Tuscany SCA
— Many articles have already been written about service-oriented architecture (SOA) and Service Component Architecture (SCA), for example, see references [1] and [2]. In this article we'll focus on a freely available, open source implementation of the Service Component Architecture that provides a simple way to implement SOA solutions. This SCA implementation is being developed in the Apache Tuscany Incubator project. The project started in 2006 and is being used by many who are looking for a simple SOA infrastructure. The recent Tuscany SCA version 1.0, which was released in September 2007, supports the Service Component Architecture specifications 1.0.

My first Quake !!!

2007-10-30T20:24:00.000-07:00

A moderate earthquake occurred at 8:04:54 PM (PDT) on Tuesday, October 30, 2007.
The magnitude 5.6 event occurred 8 km (5 miles) NNE of Alum Rock, CA.
The hypocentral depth is 9 km ( 6 miles).

Magnitude	5.6 - regional moment magnitude (Mw)
Time	Tuesday, October 30, 2007 at 8:04:54 PM (PDT) Wednesday, October 31, 2007 at 3:04:54 (UTC)
Distance from	Alum Rock, CA - 8 km (5 miles) NNE (31 degrees) Milpitas, CA - 11 km (7 miles) E (91 degrees) San Jose City Hall, CA - 15 km (9 miles) NE (45 degrees) Sunol-Midtown, CA - 17 km (10 miles) NE (45 degrees)
Coordinates	37 deg. 25.9 min. N (37.432N), 121 deg. 46.5 min. W (121.776W)
Depth	9.2 km (5.7 miles)
Location Quality	Excellent
Location Quality Parameters	Nst=250, Nph=250, Dmin=3 km, Rmss=0.07 sec, Erho=0.1 km, Erzz=0.3 km, Gp=32.4 degrees
Event ID#	nc40204628

SOA for the Business Developer: Concepts, BPEL, and SCA

2007-10-11T13:32:00.000-07:00

Ant Elder wrote on Tuscany blog :

The new book by Ben Marqolis SOA for the Business Developer: Concepts, BPEL, and SCA has been getting a lot of publicity recently so i checked it out at a local book shop. It covers both SCA and SDO, mentions Apache Tuscany, and has a focus on XML as the core of SOA and has two chapters devoted to BPEL. It is aimed more at the business user than a technical developer, but if you're looking for a book on SCA this seems to be pretty much the only thing available right now.