That sounds a lot like JSF with a JSP and a backing bean.

Arne

   To me, the main difference between event-driven applications and
non-event-driven applications are that with event-driven applications,
when someone asks you to point at the line of code that's currently
executing, it's possible for you to say that there isn't any such line,
that the system is waiting for an event to occur to trigger some
behaviour. E.g. contrast these two pseudocode listings:

Begin Program
 Print "What is your name?"
 Input $NAME
 Print "Hello " + $NAME
End Program

Begin Program
 On Key Down $KEY_ID
   Begin Subprocedure
     Print "You pressed key: " + $KEY_ID
   End Subprocedure
 On Key Up $KEY_ID
   Begin Subprocedure
     Print "You released key: " + $KEY_ID
   End Subprocedure
End Program

   With the first program, even if the program is idly waiting for input,
you can point to the "Input $NAME" line and say "This is the line that's
currently executing", whereas you can't really do the same with the second
program.

   Almost every web app I've seen is, in this sense, event-driven. Code
usually runs in response to a visitor requesting some web page. When
there's no visitors, there's no requests, and thus none of your code is
running (the server's code may be running, but I consider the server to be
a distinct application form your web app).

   - Oliver