Group items tagged

"Apache Tuscany simplifies the task of developing SOA solutions by providing a comprehensive infrastructure for SOA development and management that is based on Service Component Architecture (SCA) standard. With SCA as it's foundation, Tuscany offers solution developers the following advantages: Provides a model for creating composite applications by defining the services in the fabric and their relationships with one another. The services can be implemented in any technology. Enables service developers to create reusable services that only contain business logic. Protocols are pushed out of business logic and are handled through pluggable bindings. This lowers development cost. Applications can easily adapt to infrastructure changes without recoding since protocols are handled via pluggable bindings and quality of services (transaction, security) are handled declaratively. Existing applications can work with new SCA compositions. This allows for incremental growth towards a more flexible architecture, outsourcing or providing services to others. In addition, Tuscany is integrated with various technologies and offers: a wide range of bindings (pluggable protocols) various component types including and not limited to Java, C++, BPEL, Spring and scripting an end to end service and data solution which includes support for Jaxb and SDO a lightweight runtime that works standalone or with other application servers a modular architecture that makes it easy to integrate with different technologies and to extend Integration with web20 technologies Apache Tuscany SCA is implemented in Java and C++ (referred to as Native)"

Apache ServiceMix is an open source ESB (Enterprise Service Bus) that combines the functionality of a Service Oriented Architecture (SOA) and an Event Driven Architecture (EDA)  to create an agile, enterprise ESB. Apache ServiceMix is an open source distributed ESB built from the ground up on the  Java Business Integration (JBI) specification JSR 208 and released under the Apache license. The goal of JBI is to allow components and services to be integrated in a vendor independent way, allowing users and vendors to plug and play.

"Quercus is Caucho Technology's 100% Java implementation of PHP 5 released under the Open Source GPL license. Quercus comes with many PHP modules and extensions like PDF, PDO, MySQL, and JSON. Quercus allows for tight integration of Java services with PHP scripts, so using PHP with JMS or Grails is a quick and painless endeavor. With Quercus, PHP applications automatically take advantage of Java application server features just as connection pooling and clustered sessions. Quercus implements PHP 5 and a growing list of PHP extensions including APC, iconv, GD, gettext, JSON, MySQL, Oracle, PDF, and Postgres. Many popular PHP application will run as well as, if not better, than the standard PHP interpreter straight out of the box. The growing list of PHP software certified running on Quercus includes DokuWiki, Drupal, Gallery2, Joomla, Mambo, Mantis, MediaWiki, Phorum, phpBB, phpMyAdmin, PHP-Nuke, Wordpress and XOOPS. Quercus presents a new mixed Java/PHP approach to web applications and services where Java and PHP tightly integrate with each other. PHP applications can choose to use Java libraries and technologies like JMS, EJB, SOA frameworks, Hibernate, and Spring. This revolutionary capability is made possible because 1) PHP code is interpreted/compiled into Java and 2) Quercus and its libraries are written entirely in Java. This architecture allows PHP applications and Java libraries to talk directly with one another at the program level. To facilitate this new Java/PHP architecture, Quercus provides and API and interface to expose Java libraries to PHP. The Quercus .war file can be run on Java application servers such as Glassfish, i.e. it can be run outside of Resin. This .war file includes the Quercus interpreter and the PHP libraries."

" I am Johan den Haan, working for Mendix as CTO. This blog is personal, all opinions are mine and should be taken with a pinch of salt. I write about topics in the field of enterprise architecture and software engineering, like SOA, SOBA, MDE, MDA, MDD, DSL, etc. Johan den Haan on Twitter "

"Developing rigorous and responsive web service client applications has always been a challenge for architects and developers working with SOA. JAX-WS 2.0 comes with one effective solution to this problem: asynchronous web service invocation. In this article, we will provide an exposition of this technology with examples built upon the reference implementation. The JAX-WS programming model offers two models for invoking operations asynchronously - polling and callback. Both methods allow the client to continue processing while waiting for a response."

" Given that web service invocations are always remote across the internet, developing rigorous and responsive web service client applications has always been a challenge for architects and developers working with SOA. JAX-WS 2.0 comes with one effective solution to this problem: asynchronous web service invocation, with which a web service client may interact with a web service in a non-blocking, asynchronous approach. In this article, we will provide an exposition of this technology with examples built upon the reference implementation. Our examples utilize JDK 5.0, JAX-WS 2.0 reference implementation (RI), and Tomcat 5.5. JAX-WS 2.0 requires JAXP 1.3. To replace the JAXP 1.2 released with JDK 5.0 with this newer version, one approach is to download the JAXP 1.3 RI, and copy the endorsed directory under /lib of its installation home to %JAVA_HOME%/jre/lib. We need to copy the jaxp-api.jar of JAXP 1.3 RI to %JAVA_HOME%/jre/lib/endorsed as well. To make Tomcat 5.5 work with JAX-WS 2.0, readers need to copy all the .jar files under the /lib directory of the JAX-WS 2.0 RI installation to the %CATALINA_HOME%/shared/lib directory. As of this writing (in addition to Tomcat 5.5), Sun Java System Application Server 9.0, GlassFish, and Celtix also support JAX-WS 2.0. xFire is in the process of completing its implementation of this specification. Since asynchronous web service invocation in JAX-WS 2.0 is built upon the concurrent programming support in JDK 5.0 introduced with the java.util.concurrent package, we will start from there."

"XMPP Web Services for Java (xws4j) is an implementation of machine to machine communication over XMPP according to the XMPP Extension Protocol XEP-0244 - IO Data and others. Although the name "web services" implies network communication over HTTP all communication is carried out over XMPP. The communicated content is encoded in XML, according to customized definitions of input and output in XML Schemata. "

"The XMPP Standards Foundation is an independent, nonprofit standards development organization whose primary mission is to define open protocols for presence, instant messaging, and real-time communication and collaboration on top of the IETF's Extensible Messaging and Presence Protocol (XMPP). You can read more here."

"Qworum defines a new type of service that is used for modularizing web applications. Qworum services are interactive, just like conventional websites. In addition, Qworum services are callable, much like traditional RPC services. "

"SwitchYard is a lightweight service delivery framework providing full lifecycle support for developing, deploying, and managing service-oriented applications. Wait, what? You mean like an Enterprise Service Bus (ESB)? Yeah, kind of. At it's core, SwitchYard provides an embeddable services runtime with limited dependencies, allowing you to deploy and run services where you need them: inside unit tests, embedded in your own applications, as modules in an OSGi framework, or within an application server. Of course, there will be modular components on top of core to provide connectivity, transformation, routing and orchestration, and all the other features that are typically associated with an ESB. The main difference between SwitchYard and traditional ESB offerings is that we are trying to make the runtime a transparent detail in the service lifecycle. SwitchYard aims to keep you focused on your services by providing tooling to help define, test, and manage the important details of a service - it's contract, policies, configuration, composition, and management . After all, the least important detail of your service is where it runs."