SOA with Service Component Architecture and Enterprise Service Bus

In this article by Vincenzo Caselli, Binildas A. Christudas, and Malhar Barai, we will cover the following topics in SOA with Java:

• Service Component Architecture (SCA)
• Introduction to message-oriented middleware (MOM)
• Enterprise Service Bus (ESB)—The new architecture style
• Introduction to OpenESB

SOA with Java Business Integration (part 1)

Integration has been an area for specialists for years, since no standards exist across vendor products. This increases the Total Cost of Ownership (TCO) to implement and maintain any integration solution. Even though integration is a necessary evil, CIOs and IT managers postpone decisions and actions, and sometimes go for ad-hoc or temporary solutions. Any such activity will complicate the already confused stove pipes and it is the need of the hour to have standardization. Here we are going to inspect the need of another standard for business integration, and also look into the details of what this standard is all about.

In this article by Binildas C. A, we will look at:

• Service oriented architecture in the context of integration
• Relationship between web services and SOA
• Service oriented integration
• J2EE, JCA, and JBI—how they relate
• Introduction to JBI
• JBI Nomenclature—main components in JBI

Testing a Save As Dialog in Java using Swing

In this article by Tim Lavers and Lindsay Peters, we will be studying in detail the test for an extremely simple user interface component. It will involve UI Wrappers for components as a way of safely and easily manipulating them in tests and specific techniques for reading the state of our user interfaces. Although the component that we'll be testing in this article is simple, it will still allow us to introduce a few specific techniques for testing Swing user interfaces. It will also provide us with an excellent opportunity for showing the basic infrastructure that needs to be built into these kinds of tests.

Access Control in PHP5 CMS - Part 2

In Part 1, we had a look at the Discussion and Considerations of highly flexible role-based access control system (RBAC). In this part of the article by Martin Brampton, we will look at the database implementation. Also we will discuss the code for administering RBAC, and consider in outline how questions about access can be answered.

Binding Web Services in ESB—Web Services Gateway

Since SOI (Service Oriented Integration) is all about integrating multiple SOA-based systems, web services play a critical role in the integration space. This article is all about the importance of web services in integration. We will use the samples to illustrate how to bind web services with the ServiceMix ESB to facilitate integration.

In this article by Binildas A. Christudas, we will cover the following:

• Web services and binding
• Introduction to HTTP
• ServiceMix's servicemix-http component
• The consumer and provider roles for the ServiceMix JBI components
• servicemix-http in the consumer and provider roles
• Web service binding (Gateway) sample

Textures in Blender

In this article by Allan Brito, we will learn how to use textures to give our materials more realism. The biggest problem of working with textures is actually finding or creating a good texture. That's why, its highly recommended that you start as soon as possible to create your own texture library. Textures are mostly image files, which represent certain kinds of surfaces such as wood or stone. They work like wallpaper, which we can place on a surface or object. For instance, if we place an image of wood on a plane, it will give the impression that the plane is made of wood. That's the main principle of using textures. We will make an object look like something in the real world using a texture. For some projects, we may need a special kind of texture, which won't be found in a common library. So we will have to take a picture ourselves, or buy an image from someone. But don't worry, because often we deal with common surfaces that have common textures too.

User Input Validation in Tapestry 5

One of the benefits of having a web application is that it can be very easily accessed by everyone around the world. One of the downsides of this is that when so many people use your application, they are going to have errors in their input. Some people are not attentive, others are tired and, finally, everyone in this world has his or her individual style of thinking, so something that seems obvious to the developers of the application might puzzle someone else.

A well-designed web application should immediately be able to define that the input is wrong and stop—otherwise all kinds of errors can happen inside of the application. If this application is user-friendly, it should:

• Clearly and unambiguously inform the user that some part of the input is erroneous, and should be corrected.
• Identify the field that is erroneous and mark it in some way.
• If possible, display the erroneous value, and maybe even explain why exactly it is wrong.

In this article by Alexander Kolesnikov, we will see how Tapestry 5, being a highly efficient and user-friendly framework, handles these issues. For the purpose of this article we will use a Tapestry web application named Celebrity Collector.