Uses of Package
er.extensions

Packages that use er.extensions

er.ajax
er.attachment
er.bugtracker
er.caching
er.corebusinesslogic
er.directtoweb
er.extensions
er.googlechart	The GoogleChart framework provides WO wrappers around Google's charting API.
er.indexing
er.iui
er.javamail
er.openid
er.plot
er.prototypes
er.selenium
er.sproutcore
er.taggable	ERTaggable

Classes in er.extensions used by er.ajax

ERXFrameworkPrincipal
Designated starter class for frameworks, adds support for dependency management.
Allows you to disregard your framework order in the class path (at least where startup is concerned, if you override actual classes you still need to take care.)

The initialize() method will be called directly after your principal is instantiated.
The finishInitialization() method will be called when the app finishes startup but before it will begin to process requests.
If you define

Classes in er.extensions used by er.attachment

ERXFrameworkPrincipal
Designated starter class for frameworks, adds support for dependency management.
Allows you to disregard your framework order in the class path (at least where startup is concerned, if you override actual classes you still need to take care.)

The initialize() method will be called directly after your principal is instantiated.
The finishInitialization() method will be called when the app finishes startup but before it will begin to process requests.
If you define

Classes in er.extensions used by er.bugtracker

ERXFrameworkPrincipal
Designated starter class for frameworks, adds support for dependency management.
Allows you to disregard your framework order in the class path (at least where startup is concerned, if you override actual classes you still need to take care.)

The initialize() method will be called directly after your principal is instantiated.
The finishInitialization() method will be called when the app finishes startup but before it will begin to process requests.
If you define

Classes in er.extensions used by er.caching

ERXFrameworkPrincipal
Designated starter class for frameworks, adds support for dependency management.
Allows you to disregard your framework order in the class path (at least where startup is concerned, if you override actual classes you still need to take care.)

The initialize() method will be called directly after your principal is instantiated.
The finishInitialization() method will be called when the app finishes startup but before it will begin to process requests.
If you define

Classes in er.extensions used by er.corebusinesslogic

ERXFrameworkPrincipal
Designated starter class for frameworks, adds support for dependency management.
Allows you to disregard your framework order in the class path (at least where startup is concerned, if you override actual classes you still need to take care.)

The initialize() method will be called directly after your principal is instantiated.
The finishInitialization() method will be called when the app finishes startup but before it will begin to process requests.
If you define

Classes in er.extensions used by er.directtoweb

ERXFrameworkPrincipal
Designated starter class for frameworks, adds support for dependency management.
Allows you to disregard your framework order in the class path (at least where startup is concerned, if you override actual classes you still need to take care.)

The initialize() method will be called directly after your principal is instantiated.
The finishInitialization() method will be called when the app finishes startup but before it will begin to process requests.
If you define

Classes in er.extensions used by er.extensions

ERXFrameworkPrincipal
Designated starter class for frameworks, adds support for dependency management.
Allows you to disregard your framework order in the class path (at least where startup is concerned, if you override actual classes you still need to take care.)

The initialize() method will be called directly after your principal is instantiated.
The finishInitialization() method will be called when the app finishes startup but before it will begin to process requests.
If you define

Classes in er.extensions used by er.googlechart

ERXFrameworkPrincipal
Designated starter class for frameworks, adds support for dependency management.
Allows you to disregard your framework order in the class path (at least where startup is concerned, if you override actual classes you still need to take care.)

The initialize() method will be called directly after your principal is instantiated.
The finishInitialization() method will be called when the app finishes startup but before it will begin to process requests.
If you define

Classes in er.extensions used by er.indexing

ERXFrameworkPrincipal
Designated starter class for frameworks, adds support for dependency management.
Allows you to disregard your framework order in the class path (at least where startup is concerned, if you override actual classes you still need to take care.)

The initialize() method will be called directly after your principal is instantiated.
The finishInitialization() method will be called when the app finishes startup but before it will begin to process requests.
If you define

Classes in er.extensions used by er.iui

ERXFrameworkPrincipal
Designated starter class for frameworks, adds support for dependency management.
Allows you to disregard your framework order in the class path (at least where startup is concerned, if you override actual classes you still need to take care.)

The initialize() method will be called directly after your principal is instantiated.
The finishInitialization() method will be called when the app finishes startup but before it will begin to process requests.
If you define

Classes in er.extensions used by er.javamail

ERXFrameworkPrincipal
Designated starter class for frameworks, adds support for dependency management.
Allows you to disregard your framework order in the class path (at least where startup is concerned, if you override actual classes you still need to take care.)

The initialize() method will be called directly after your principal is instantiated.
The finishInitialization() method will be called when the app finishes startup but before it will begin to process requests.
If you define

Classes in er.extensions used by er.openid

ERXFrameworkPrincipal
Designated starter class for frameworks, adds support for dependency management.
Allows you to disregard your framework order in the class path (at least where startup is concerned, if you override actual classes you still need to take care.)

The initialize() method will be called directly after your principal is instantiated.
The finishInitialization() method will be called when the app finishes startup but before it will begin to process requests.
If you define

Classes in er.extensions used by er.plot

ERXFrameworkPrincipal
Designated starter class for frameworks, adds support for dependency management.
Allows you to disregard your framework order in the class path (at least where startup is concerned, if you override actual classes you still need to take care.)

The initialize() method will be called directly after your principal is instantiated.
The finishInitialization() method will be called when the app finishes startup but before it will begin to process requests.
If you define

Classes in er.extensions used by er.prototypes

ERXFrameworkPrincipal
Designated starter class for frameworks, adds support for dependency management.
Allows you to disregard your framework order in the class path (at least where startup is concerned, if you override actual classes you still need to take care.)

The initialize() method will be called directly after your principal is instantiated.
The finishInitialization() method will be called when the app finishes startup but before it will begin to process requests.
If you define

Classes in er.extensions used by er.selenium

ERXFrameworkPrincipal
Designated starter class for frameworks, adds support for dependency management.
Allows you to disregard your framework order in the class path (at least where startup is concerned, if you override actual classes you still need to take care.)

The initialize() method will be called directly after your principal is instantiated.
The finishInitialization() method will be called when the app finishes startup but before it will begin to process requests.
If you define

Classes in er.extensions used by er.sproutcore

ERXFrameworkPrincipal
Designated starter class for frameworks, adds support for dependency management.
Allows you to disregard your framework order in the class path (at least where startup is concerned, if you override actual classes you still need to take care.)

The initialize() method will be called directly after your principal is instantiated.
The finishInitialization() method will be called when the app finishes startup but before it will begin to process requests.
If you define

Classes in er.extensions used by er.taggable

ERXFrameworkPrincipal
Designated starter class for frameworks, adds support for dependency management.
Allows you to disregard your framework order in the class path (at least where startup is concerned, if you override actual classes you still need to take care.)

The initialize() method will be called directly after your principal is instantiated.
The finishInitialization() method will be called when the app finishes startup but before it will begin to process requests.
If you define