SOA governance is the combination of people, policies, and processes within your organization that will ensure that the desired behaviors of your strategic SOA initiative are achieved.It includes the traditional areas associated with IT Governance, which is the selection and funding of IT projects. These projects define the initial scope for technology utilization and can either help or hinder the SOA effort, based upon the scope chosen. In this article by Todd Biske we will see that the SOA effort only gets executed through projects, and if the execution is poor, the SOA effort will be poor. Therefore, the project governance activities of an organization must be adjusted to include policies associated with achieving the desired behaviors associated with SOA adoption.
Advasco had initial success with their Customer Information Service and then opened the flood gates for development by the rest of the organization. These efforts were successfully reigned in by the newly formed Center of Excellence. Now, the team at Advasco faces a new challenge: modifying an existing service to handle the needs of a new consumer. This article will go over the challenges faced by the team and then present guidance for handling this situation within your own organization.Read Service Versioning in SOA in full
The Drupal system, when combined with the PHPTemplate engine, gives you the ability to create logic that will automatically display templates or specific elements in response to the existence of certain conditions. In this two part article by Ric Shreves, we will look at running multiple templates, and at creating dynamic elements and styles. Among the techniques covered in these articles ( Part 1 and Part 2 ) are: using suggestions—naming conventions—to control template display, the use of $body_classes to create dynamic styling, and the implementation of the preprocessor function.Read Dynamic Theming in Drupal 6 - Part 1 in full
A Layout turns your forms, grids, and other widgets into a true web application. The most widely-used layout styles can be found in operating systems such as Microsoft's Windows, which uses border layouts, resizable regions, accordions, tabs, and just about everything else you can think of.
To keep looks consistent between browsers, and to provide common user interface features, Ext JS has a powerful layout management system. The sections are manageable, and can be moved or hidden, and they can appear at the click of a button, right when and where you need them to.
In this article by Shea Frederick, Steve 'Cutter' Blades, and Colin Ramsay, we will learn to:
- Lay out an application style screen
- Create tabbed sections
- Manage Ext widgets within a layout
- Learn advanced and nested layouts
Minilang can help developers to reduce the time it takes to implement simple and repetitive tasks. Code does not need to be compiled and can therefore be implemented faster, breaking the typical Java code-compile-test cycle. Minilang gives the advantage of being able to change the code without a restart of the application. A simple browser refresh is enough to see the changes.
It is more "plain English" than Java code and is simpler to read and therefore easier to understand and maintain by people who may be unfamiliar with the system.
The main reason for Minilang's existence is to facilitate simple operations, notably CRUD operations and to validate and manipulate data. It should not be much used outside of this scope, but within this scope, it excels.
In this article by Jonathon Wong and Rupert Howell we will be looking at:
- Minilang syntax and schema
- Defining and creating a "Simple Service" using Minilang
- Simple events
- Validating and converting fields using the simple-map-processor
- Security in Minilang
- Invoking other services, methods, events, and BeanShell from Minilang
- Using Minilang in screen widgets
The Java Persistence API (JPA) is an object relational mapping API. Object relational mapping tools help us automate mapping Java objects to relational database tables. Earlier versions of J2EE used Entity Beans as the standard approach for object relational mapping. Entity Beans attempted to keep the data in memory always synchronized with database data, a good idea in theory, however, in practice this feature resulted in poorly performing applications.
Several object relational mapping APIs were developed to overcome the limitations of Entity Beans, such as Hibernate, iBatis, Cayenne, and Toplink among others.
With Java EE 5, Entity Beans were deprecated in favor of JPA. JPA took ideas from several object relational mapping tools and incorporated them into the standard. As we will see in this article by David Heffelfinger, NetBeans has several features that make development with JPA a breeze.Read Interacting with Databases through the Java Persistence API in full