:::: MENU ::::
Browsing posts in: JEE6

Separation of concerns

Separation of concerns is at the core of software engineering in general, and of object-oriented software development in particular. Done well, it can provide a host of crucial benefits: additive, rather than invasive, change; improved comprehension and reduction of complexity; adaptability, customizability, and reuse, particularly of off-the-shelf components; simplified component integration; and the ultimate goal of “faster, safer, cheaper, better” software.

 

To benefit fully from separation of concerns, one must have the right modularization at the right time; the concerns that are separated must match the concerns one needs to deal with. Unfortunately, different development activities often involve concerns of dramatically different kinds. For example, changing a data representation in an object-oriented system might involve a single class, or a few closely-related classes, and might be done additively using subclassing or suitable design patterns. Here the hallmark of object orientation – modularization (or object) – is a major asset. On the other hand, adding a new feature to a system typically involves invasive changes to many classes: the feature code is scattered across multiple classes; and tangled with other code within those classes. This reduces comprehensibility and increases impact of change and the likelihood of error. In short, one needs different modularizations for different purposes: sometimes by feature, sometimes by aspect (e.g., distribution or persistence), role, variant or other criterion.

 


Fast Lane Reader

I share with all of you this interesting design pattern, which is mostly used when you want to query your DB as quick as possible in Web apps 3-Tier, at least, of course…


Companies Increasingly Need the Internet to Compete

Through the next decade, most business transactions will be conducted over the Internet. To make this work on a grand scale, standards are critical. The success of JEE is important because it ensures that the Internet is the most cost-effective medium to use for promoting the services of a business. Conducting business with a user-friendly, reliable, speedy, and attractive set of web pages supported by reliable back-end business logic will make the difference between success and failure in the enterprise business.
The entire business must be Internet enabled. The business site must engage the customers and enable them to conduct transactions without the necessity of human interaction. Moreover, it will feed the organization’s “fulfillment” engine as well as provide a place to go for post-transaction services.
Corporations will need architects to anchor development standards such as JEE to facilitate the construction of websites. These sites will communicate the business objectives of their clients, whether they want to direct functionality to local, national, or international markets.
Development roles are now more important than ever. The architect must work together with other technical and graphic design personnel to ensure that the web pages not only meet the business’s needs but that they also maintain a perfect balance between performance and professional graphics work. The design of each component must follow a standard such as JEE to ensure that the end product looks professional, loads faster, and effectively communicates the company’s business objectives to the world.

Similarities of JEE and Oracle ADF

ADF is built on top of the Java and Java EE stack. If you are familiar with Java EE, this topic is for you. Let us take a quick look at the basic building blocks of these two technologies to see what they have in common:

similarities