You don't have to create a form bean if you don't want or need to. In your
example, the form bean would only have one property, and that property came
directly from a link (minimizing the risk of invalid values, and hence the
need for validation in the form bean), so you could just use
request.getParameter() instead if you wanted to.
Regarding "unifying" access to form fields and parameters, I'm not sure what
you're getting at. If a form bean is used, Struts will populate it from the
request parameters regardless of how the request was submitted. So long as
the form bean has a property corresponding to each parameter name, the form
will contain all of the request parameter values when your action class is
called.
--
Martin Cooper
- Original Message -
From: "Andreas Leitner" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, July 25, 2001 1:13 AM
Subject: Newbee: design question
>
> Hi,
>
> I am pretty new to tomcat/struts but nevertheless trying to create a
> simple application using the two (; I have troubles getting my design
> right, maybe some people on this list could give me some hints, they
> would be greatly appreciated.
>
> The idea is that I have a DB backend that stores a bunch of documents
> identified by an integer. Now the user can click on a link and view the
> document (that's the first step). Now the link looks like this:
>
