I gather that this is frowned upon:
<forward name="resolution" path="/resolveName.do" />
However, when I wrote the app, I couldn't find a way around it. The
flow is that you type a name in field 1 on form A, you get a list of
possible matches, and you pick one and return to form A which inserts
that name in field 1.
The complication is that there are multiple fields on form A that need
this behavior. And then there's form B and C that also need to use this
name resolution.
I had to resort to sticking String in request scope and using that as
the target of the resolution form (which isn't a Struts form):
<form action="<c:out value="${returnTo}"/>" method="POST">
I'm using a recent nightly build. Is there anything in there that can
solve the "go back where you came from" problem? And once you get back
where you came from, I also need to know which field you were trying to
resolve.
If it sounds like a mess, it is! (But it's working...)
--
Wendy Smoak
Applications Systems Analyst, Sr.
Arizona State University, PA, IRM
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
