>>>>> "David" == David M Karr <[EMAIL PROTECTED]> writes:
>>>>> "David" == David M Karr <[EMAIL PROTECTED]> writes:
David> Tomcat3.2.3 (with JBoss2.4.1).
David> I have several architectural and technical issues I'm trying to resolve
with a
David> quite simple page arrangement. I'd appreciate any guidance, both towards
David> fixing what I have, and producing a more "sane" arrangement, if there's
David> something basicallywrong with my architecture.
David> Update:
David> I realized that my "perform" method was looking for the "forward" in the
David> servlet, instead of the ActionMapping. Once I fixed that, the initial
display
David> of the class list worked fine.
David> Then, I clicked one of the Edit buttons, changed one of the fields, clicked
the
David> Save button, and it displayed the following error:
Well, I ended up adding code in my "SaveClassAction" class which just manually
gets the "listClassesForm" attribute from the session, and then updates the
attribute on it manually, then continues with the forward. That correctly
updates the list after I click "Save".
It almost seems like "forwards" bypass actions. When I did my "forward" back
to the list page, it wouldn't execute the "ListClassesAction.perform()" method,
which normally populates the list with new data.
Is there a cleaner strategy for doing things like this? I definitely didn't
like to hardcode the reference to "listClassesForm" in the
"SaveClassAction.perform*()" method. I wish I could have gotten some sort of
indirect reference to the form bean associated with the page I was going to
forward to.
--
===================================================================
David M. Karr ; Best Consulting
[EMAIL PROTECTED] ; Java/Unix/XML/C++/X ; BrainBench CJ12P (#12004)
