Services

Projects

Clients

About Us

Lolay at JavaOne 2001

If you checked out this years JavaOne conference you might have seen our Birds of a Feather. If you're looking for more information, you've come to the right place.

Visit the Capsule product (open-sourced) for source code, newsgroups and etc.

You can get a zip'ed copy of the presentation slides here.

The presentation was given by Gary Rudolph (gary@lolay.com) of Lolay and Shannon Thornton (shannon.thornton@nextel.com) of Nextel Communications.

BOF - "J2EE Use Case Framework: In between a session and request"

With more internal business systems/processes being converted to Internet applications many developers are faced with the difficulty of managing complex business logic user interfaces. Many insurance systems, medical systems, telecommunication rate plan and billing systems are all moving to Internet deployed applications. Traditional Internet applications have never had to deal with the level of complexity required in moving business processes to the web. This type of development is becoming more prevalent in the industry.

The J2EE specification and various implementations support the concept of request and session scope data. This has greatly increased the productivity of developers on traditional applications, but on more complex applications modeled with complex use case interactions something more is needed. Request data is often too short lived. Session data is typically too long lived, and unfortunately too "global".

This session discusses an advanced design of a use case framework that was implemented on a rate plan approval system that was moved to J2EE technology at Nextel Communications. The framework focuses on easily converting business analyst use case designs into use case software components that can easily be developed by different development teams as black box efforts. The framework creates a new scope of data named use case data (built upon the J2EE session data) that is isolated only to the use case component in action. The use case scope data is automatically preserved and restored when nesting (invoking) another use case component inside another use case. This prevents the invoked use case from modifying any data used by the invoking use case. This greatly increases the productivity of debugging concurrent black box development on different use case components.