Matt, In the posted example for the Struts 2 project there seems to be an issue with the PersonAction where things are done in terms of the id on the action. Trouble is this gets set, and then on a subsequent request it winds up being null. So the call to save always creates a new row in the table. I solved this by storing the id in the session when the setter setId gets called. In fact many of the methods in the PersonAction now look for the id being in the session vs. just looking at the instance id variable. Am I losing my mind or should the example be updated?
Thanks, Ryan
