> I'm not sure I understand what you mean by the "input level". Could you
> describe it further?
First, my understanding of Struts is that actions happen at the form level,
such that a form action is further inspected to determine what needs to be
done. In my system, I go to the lower level of granularity to the actual
input events.
Let's say I have a form. On that form I can do a few actions, namely Update,
Add, and Delete. In my architecture, I have it like so:
<input type="submit" name="formname.update" value="Update">
<input type="submit" name="formname.add" value="Add">
<input type="submit" name="formname.delete" value="Delete">
The form is posting to:
<form name="formname" action="/AppServlet" method="post">
Right now, those actions are separate objects but I'm not to sure I like
that, but I'm also not a fan of runtime introspection. My goal, though, is
to remove most, if not all, switch-like logic. Also, I'm trying to get my
application flow to become as far removed as possible, since one of my goals
is to make an application mapping app.
Anyway, I hope this makes some sort of sense. Getting an understanding of
the motives of Struts while trying to keep what I like about my stuff is a
prescription for headaches.
George Lessmann
Ponvia Technology, Inc
