Hey - I wish I'd had that when I started with Struts! I don't personally agree with your philosophy on setting autoCommit to true, but I liked the page other than that :-) <click>Add Bookmark</click> I just feel having autoCommits off is a good thing. That way you have explicit control over the transaction. If, however, you typically don't need it, I can understand setting autoCommit(true). Maybe I'm just too anal ;-)
Thanks :-) Eddie Roman Fail wrote: >This is the very basic outline of Struts events (with some helpful comments) that I >worked up when I was using Struts 1.0, although most of it is still the same. >Basically I've just expanded steps 3 & 4 of Dan's diagram a bit. Chapter 5 of >Chuck's book is much more detailed than this, and an excellent resource (Thanks, >Chuck!). In fact I think chapter 5 might be a bit overwhelming for a newbie, and >reading the ever-changing Struts source code is not comfortable at first. > >I've found that this little outline has helped our new Struts developers a lot. >Craig suggested a nice UML sequence diagram for the docs, which would be great - but >I'm not fluent in UML yet. Here's my document - keep in mind it's been about a year >since I wrote this, but I'd be happy to take suggestions on updating it: > >http://www.posportal.com/StrutsOverview.html > >Roman Fail >Sr. Web Application Developer >POS Portal, Inc. > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
