On 7/18/05, Frank W. Zammetti <[EMAIL PROTECTED]> wrote: > I used to do a lot of this back when I wasn't as clear on why Actions > shouldn't contain actual code (this started when I was using a custom > framework my company build that had examples that didn't make it clear > you shouldn't do this). >
Exactly what I've ran into as well! Most of the time I end up refactoring almost all non-trivial logic into separate classes because I have needed them elsewhere. What the original poster may be able to get away with is making the method public static in the action. It's a hack, but it will get you running quickly. Once you get it tested and working it's easy to move the method(s) to a helper class, espcially if you are using an IDE that supports refactoring like Eclipse or IDEA. Don't make them static if they depend on session or request state, as you'll shoot yourself in the foot due to the implicit threading in the app server. Good luck! -ed --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
