> You wouldn't want to hit the JSP first anyways ;-). It was suggested by another person here and I just wanted to rule it out in case it was your next suggestion. :)
> I believe both of your > thoughts will work but I would try the separate action mapping idea first. I did, and it works, but... BLECH! I have to duplicate every single action mapping?! And what am I supposed to call them? someAction.do is so clean, and now I have to have someActionFirstTime.do? Or perhaps I keep the first one with the clean name and call the others someAction2? I'm examining the struts-example with JSP's under WEB-INF, and I think the difference is my use of LookupDispatchAction vs. separate Actions for each thing: edit/save/create. This particular form isn't a CRUD form, it's a "Select the person you want to view read-only info on", so I can't quite make the createSomething, editSomething, updateSomething pattern fit. And it kind of defeats the purpose of LookupDispatchAction to have to map it several times. I'm still pondering what to do about this. I'm currently going with someAction.do and someActionNV.do (for No Validation). Ideas appreciated! -- Wendy Smoak Applications Systems Analyst, Sr. Arizona State University PA Information Resources Management
