|
Sponsored Links
Resources
Enterprise Java
Research Library
Get Java white papers, product information, case studies and webcasts
|
News
News
News
|
Messages: 13
Messages: 13
Messages: 13
Printer friendly
Printer friendly
Printer friendly
Post reply
Post reply
Post reply
XML
XML
XML
|
 |
Apache Tuscany is now an official ASF project
Apache Tuscany is a project which combines various technologies including an implementation of the OASIS OpenCSA "Service Component Architecture (SCA)" standard to simplify the development, deployment and management of distributed applications built as compositions of service components.
Apache Tuscany has been incubating for over two years at Apache. Graduating to a top level Apache project is a significant milestone and further endorsement of the already successful project.
After a bit of a slow start SCA now looks like it has a bright future. There is growing recognition of the utility of SCA and most vendors in the SOA space are planning to introduce support for it in their products. Sun remains one of the few unconvinced but even there there is now a burgeoning user driven effort trying to change that.
Can you afford not to know about SCA? Apache Tuscany is now the premier open source implementation, come check it out!
|
|
|
Message #253394
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: SCA vs. OSGI
Try looking at Newton, it combines SCA, OSGi and Jini. My combining the three, perhaps it will become clearer where each serves its purpose... :))
|
|
|
Message #253405
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: SCA vs. OSGI
SCA sounds like OSGI. What's the difference?
They each address different areas. SCA is about assembling applications out of components with the component interaction QOS policies and communication protocols defined declaratively. OSGi is about running services and managing their versions and dependencies. So they are complementary, with SCA being at a higher level. You can use OSGi within SCA, and OSGi could be used to build an SCA environment.
OSOA has a whitepaper, Power Combination: SCA, OSGi and Spring, which describes this in more depth.
|
|
|
Message #253481
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: SCA vs. OSGI
Thanks. I hope I will not be forced to go into these "simple", "leightweight" technologies.
Right. If a technology claims "lightweight" as its most important trait, be dubious. Very dubious.
You can't walk around complexity by imagining it doesn't exist.
|
|
|
Message #253640
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: SCA vs. OSGI
Thanks. I hope I will not be forced to go into these "simple", "leightweight" technologies.
Right. If a technology claims "lightweight" as its most important trait, be dubious. Very dubious.
You can't walk around complexity by imagining it doesn't exist.
There was no reference to "lightweight" in this post about Tuscany so whats with all these comments? Of all the qualities and attributes of Tuscany and SCA the weightiness is not one of the major features.
|
|
|
Message #253697
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: SCA vs. OSGI
Thanks. I hope I will not be forced to go into these "simple", "leightweight" technologies.
There was no reference to "lightweight" in this post about Tuscany so whats with all these comments? Of all the qualities and attributes of Tuscany and SCA the weightiness is not one of the major features.
I think it started when somebody mentioned the whitepaper about SCA/OSGI/Spring. Spring is often described by its fans as "lightweight", though some of us might disagree.
|
|
|
Message #253705
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Lightweight?
Well, maybe it came from the website which describes Tuscany as being a, "lightweight runtime...designed to be embedded in, or provisioned to, a number of different host environments without much effort" (http://incubator.apache.org/tuscany/sca-java.html)?
I took the trouble to download Tuscany and discovered it was over 60MB with 150+ third-party dependencies. Based on this, the criticisms seem fair. Tuscany is hardly lightweight.
Another thing is the post sounds as if it came out of some jargon-mill: "...simplify the development, deployment and management of distributed applications built as compositions of service components." You guys would be better served describing what Tuscany does in plain terms.
|
|
|
Message #253762
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
What Tuscany is ... sort of
Fair points about the descriptions of SCA/Tuscany being more than a bit vague. It slices, it dices, it makes your teeth whiter, it makes your lawn grow in thicker and women love a man who's got Tuscany.
Probably the best way to think of it is as a service composition tool. It goes beyond orchestration/workflow (though it addresses that too). Imagine you've got six different components you want to stitch together to build a composite application -- stuff like a price calculator, inventory, payment processor, customer history, etc. Somebody previously had to code those components and tackle the complexity. Maybe someone has to go in an build another component or two for the new composite app to get up and running.
What Tuscany does is give you a framework to put all of that together and let each component run wherever it runs. Provided you've built components with the right granularity (in this case large), it should be easy enough to swap out components or change the app on the fly. Here's the summary I wrote on the JavaOne Tuscany presentation.
What complexity it eliminates is mostly on the integration side. A little Atompub and A is talking to B in a jiffy. It aims to simplify the middle. Technically a non-developer could take care of the Tuscany composition, leaving your developers to tackle complexity within the individual components. Ideally it will mean less busywork for developers.
I make no representations that it will all work as advertised. Almost nothing does. I imagine some effort will be required in making sure a component is Tuscany-consumable.
|
|
|
Message #254741
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: SCA vs. OSGI
What's more, SCA even has a Dependency Injection mechanism of its own! Like having all those other DI systems was not enough! To count a few of them: spring, seam, webbeans, jsf managed beans, OSGI service lookup stuff, ..., and now SCA's DI stuff. Soon we'll see apps with potentially 3 or 4 different but similar ways of DI in them! Nice!
Ara.
|
|
|
| New content on TheServerSide.comNew content on TheServerSide.comNew content on TheServerSide.com |
|
|
Reza Rahman continues to explore the features of the proposed JSR 299, Contexts and Dependency Injection for Java EE (CDI). When approved, it promises to be a key feature of Java EE 6.
(January 21, Article)
Ted Neward is an independent consultant specializing in high-scale enterprise systems, and an authority in Java and .NET technologies. He is the author and co-author of several books, including Effective Enterprise Java. At TheServerSide Java Symposium in March, he will be presenting sessions on pragmatic architecture, ECMAScript and Scala.
(January 15, Article)
Now that Oracle is absorbing Sun Microsystems, there mixed views on what should come of the Java Community Process (JCP). While some say Oracle should become the new steward of Java and keep the JCP much as it was, others argue that it may be time to open-source this widespread language.
(November 24, Article)
Reza Rahman explores the features of the proposed JSR 299, Contexts and Dependency Injection for Java EE (CDI). When approved, it promises to be a key feature of Java EE 6.
(November 2, Article)
SAML is an XML-based standard for exchanging authentication and authorization data between security domains. The single most important problem that SAML was created to solve is the Web browser Single Sign-On problem. Many organizations are debating whether to stay with version 1.1 or move to 2.0. This article makes observations about both options.
(September 28, Article)
Joe Ottinger takes a look at how people learn, and applies it to the practice of programming. He notes that understanding how people learn is an essential part of working in a programming team.
(September 22, Article)
Stephen Maryka gave us an article about the Asynchronous Web and posed a number of questions that get examined like an approach to delivering Asynchronous Web capabilities through extensions to existing Java EE technologies.
(July 14, Article)
JavaServer Faces Flex goal is to provide users capability in creating standard Flex components, part of flexSDK which is open sourced through MPL license, as normal JSF components. This article by Ji Hoon Kim will provide an overview of creating a simple multilingual JSF page consisting of JSF Flex tags.
(June 29, Article)
In this session Jeff explores the key characteristics of successful SOA projects. He covers some of the patterns, and anti-patterns, tool sets, and strategies that he himself learned the hard way. Last, he provides a strategy and blueprint for achieving a high likelihood of success in your SOA project.
(June 23, Tech Talk)
Ari Zilka, CTO of Terracotta, Inc., talks about the new features in Terracotta 3.1, announced during JavaOne and available now.
(June 15, Tech Talk)
In this Tech Talk, Josh Long explores an integration challenge using Spring Integration and walks through the implementation, employing and expanding on the basic patterns of Enterprise Application Integration to tie together components into a function integration solution, and then demonstrates how Spring Integration helps address the integration requirements.
(June 15, Tech Talk)
In this Tech Talk, David Geary teaches you: The basics of Google Web Toolkit; How to implement Ajax-enabled applications in Java; Internationalization; Hooking into the browser history mechanism; Remote procedure calls.
(June 4, Tech Talk)
Jon Kern discusses the best architecture/technical solutions and ensure that they are repeated by all developers. By tackling the architecture up-front in a serial manner, subsequent parallel development will be much more manageable and predictable.
(May 28, Tech Talk)
This keynote describes the frustrations of modern knowledge workers in their quest to actually get some work done, and solutions for how to guard yourself against all those distractions. Neal Ford talks about environments, coding, acceleration, automation, and avoiding repetition as ways to defeat the misguided attempts to sap your ability to produce good work.
(May 26, Tech Talk)
Gil demonstrates how new, aggressive uses of already abundant compute capacity by common applications offer competitive value for application designers.
(May 21, Tech Talk)
Chris Keene introduces WaveMaker as a new way to automate the ability to generate Hibernate classes in order to more quickly bring OR mapping into an application.
(May 19, Article)
Mastering EJB was one of the original and most influential EJB books in the industry. Mastering EJB III now returns with two new expert co-authors, updated for EJB 2.1 and 30% new chapters including security, integration, best practices, open source, and more.
(Book PDF Download)
The Application Server Matrix is a detailed listing of J2EE vendors and their application server products, with information on latest version numbers, J2EE spec support and licensing, pricing, platform support, and links to product downloads and reviews.
(Application Server Comparison Matrix)
|
|
