AppFuse:
Igniting your applications with AppFuse

by
Ryan Withers, Senior Software Engineer
Object Computing, Inc. (OCI)
Introduction

"How soon can you have it done?" Sound all too familiar? Managers over
the years have been faced with ever increasing demands to produce more
software over shorter delivery cycles. As the economic landscape has
gone global, these pressures to deliver have increased dramatically.
For software developers this results in a responsibility to achieve
the highest levels of productivity. Given this, any well meaning
developer must constantly search for the appropriate tools for the
job. In the world of J2EE, many of us find ourselves writing a little
code, adding a little configuration, writing a little code, adding a
little configuration, so on and so forth. Much of our time is spent
worrying about configuration, and this is time better spent on
business logic. Time spent configuring does not translate well into
real value. In addition, it has a huge associated risk, in that
configuration errors can introduce problems. In addition, writing the
wrote boilerplate code to glue together the various layers of a system
can be time consuming and monotonous work. If this sounds familiar,
read on to see how AppFuse can accelerate development cycles, and help
to mitigate the risks associated with configuration heavy projects.

AppFuse provides standard project templates, code generation, and a
shell of application code to get projects up and running quickly. One
of its primary strengths is the automation of configuration and setup,
two things standard in most J2EE projects. This article will show the
following three things: First, we will create a shell project. Second,
we will extend the project by hand, adding a basic time tracking page.
Third, we will wipe the slate clean, and create the same time tracking
page again. Only this time we will use the appgen tool to perform
complete code generation of the whole thing.

You can find the rest of this article at
http://www.ociweb.com/jnb/jnbMay2008.html

Best regards,
Lance Finney