RAD tool
Plan
|
Forged on: |
|
|
|
The
tool development is planned in the following stages. Stage1 has been implemented
and is ready. The other stages are to follow. 1)
Stage1: Development of the core tool (READY) with following
features.
a) Deployment descriptors (code metadata files) for i)
Generating wrapper classes
of different types and supporting containership i.e. wrappers that have wrappers
as data members in addition to normal fields. ii)
Generating builder classes that perform server side validation, error
handling on form data and populate the wrapper class instances iii)
Specifying handler properties which includes details like what builder to
use, access roles (JAAS), what to do on successful validation, what to do on
custom validation, what to do with the result obtained from the database or any
other source. iv)
Mapping web requests to a handler class v)
Declaratively choosing whether security will be vide JAAS or session
management. vi)
Declaratively specify which roles (out of the permitted roles) can access
which request when using JAAS. b)
The user developer needs to code only the following. i)
A handler class that extends a base handler class and provides
implementation of specific methods (1)
For business logic (database
access etc), (2)
Custom validation (if any that is not covered declaratively), (3)
Formatting any success
message (if needed) ii)
Write the jsp, which uses the data sent to it by the handler. 2)
Stage2: additional features of the core tool. a)
Providing a deployment property to choose between parameterized error
messages and non-parameterized error messages
. b)
Provide object Inheritance in wrapper classes. Right now wrapper classes
of RAD only support containership. c)
Incorporate JavaScript also in the output web-application d)
Enhance a few other components in RAD framework e) Provide a very sophisticated (but unusual) presentation components editor for use with jsp taglibs. f) Provide a refresh control g) Also demonstrate usage of JSTL and Struts html tags as an option to the regular radtool presenation feature in the radtool framework.
3)
Stage3: declaratively provide following. a)
Persistence using a simple in-built persistence layer. b)
Persistence with a standard JDO implementation c)
Persistence with specific ejb servers for database access d)
Provide a state machine for managing session specific information. e) Manage LDAP integration. 4)
Stage4: Use RAD itself to build a J2EE web application and webstart
application based IDE for managing the code and deployment descriptors.
|
|
Send mail to raghu121@hotmail.com with
questions or comments .
|
![[Under Construction]](images/undercon.gif){kind=small}