"Write beautiful code; then profile that beautiful code and make little bits of it uglier but faster." --The JavaPerformanceTuning.com team, Newsletter 039.
Originally posted by Dave Hewitson:
I understand what your saying, but the other problem is that in my action when I want to progress from screen A to screen B, my forward is linked to a screenB.do in the config file.
"Write beautiful code; then profile that beautiful code and make little bits of it uglier but faster." --The JavaPerformanceTuning.com team, Newsletter 039.
Originally posted by Matthew Marquand:
Chaining actions to actions has been discussed as a bad practice.
Originally posted by Jason Menard:
<hijack>
Interesting. Do you have any links to any discussions on this, or any other references?
</hijack>
"Write beautiful code; then profile that beautiful code and make little bits of it uglier but faster." --The JavaPerformanceTuning.com team, Newsletter 039.
Originally posted by Dave Hewitson:
David - wrt "progress from screen A to screen B", I mean simply doing a forward in the actionA, but in this case the forward is screenB.do rather than screenB.jsp - in this way I can do some screen preprocessing in the screenB action, and then use another forward to the jsp.
"Write beautiful code; then profile that beautiful code and make little bits of it uglier but faster." --The JavaPerformanceTuning.com team, Newsletter 039.
Don't get me started about those stupid light bulbs. |