Sun Logo


Suntrademark ONE Application Framework Overview

Suntrademark ONE Studio 5 update 1

817-4360-10



Contents

Preface

How This Book Is Organized

Using UNIX Commands

Related Documentation

Accessing Sun Documentation

Contacting Sun Technical Support

Sun Welcomes Your Comments

1. Sun ONE Application Framework Overview

Introduction: The Challenges of Building Web Applications

Building Web Applications: Pre-J2EE

Building Web Applications: Post-J2EE

Emergence of the J2EE Application Framework

The Criteria of an Enterprise Application Framework

What is the Sun ONE Application Framework?

Overview

Who Should Be Interested in the Sun ONE Application Framework?

What Does the Sun ONE Application Framework Do?

What Doesn't the Sun ONE Application Framework Do?

How Does the Sun ONE Application Framework Work?

Use of Design Patterns

Types of Functionality

How is the Sun ONE Application Framework Different From Other Web Application Frameworks?

Based on J2EE Standards

A Familiar Paradigm

Application Consistency

Symmetrical Display/Submit Handling

Formal Model Entity

Application Events

Hierarchical Views and Component Scoping

Efficient Object Management

Support for Parallel Content

Ready-to-Use, High-Level Features

Tool-ready

Enterprise-class Performance

Conclusion

2. Sun ONE Application Framework Design and Architecture FAQ

Who should be interested in the Sun ONE Application Framework?

Why use the Sun ONE Application Framework when you already have J2EE?

Isn't the Sun ONE Application Framework just another proprietary Web Application Framework (JAPWAF)?

How is the Sun ONE Application Framework different from other J2EE frameworks?

The Sun ONE Application Framework has the notion of a display field. This isn't like the J2EE Blueprints or other J2EE architectures I've seen--why not just pull values directly from a helper bean?

Do the Sun ONE Application Framework applications require the use of EJBs?

How are the Sun ONE Application Framework applications structured?

How are the request flow and URL format implemented?

How does a view bean relate to a session or entity bean?

With the JSP scope set to request to simplify threadsafe coding and force beans to be constructed and destroyed with each request, will there be negative performance impact?

Index