--- Jonathon -- Improov <[EMAIL PROTECTED]> wrote: > > > or you may find it easier to accomplish what you're wanting > through a > > java method > > Not this, it requires a recompile and OFBiz restart.
I'm saying you create your one time java class that does the recursion, then you have it available forever and don't need to play with the community code. Thus separating the application logic from the business logic. Java and simple methods can be mixed quite nicely at times. > > > 3. final thoughts... > "Private scope" calls (callee has private scope) are cleaner and > easier to program than "global > scope" calls (mere macros). Simple analogy. Suppose your office hires > my company to do work, and > you have a Jonathon and I have a Jonathon here too. You send me this > instruction: "Get Jonathon to > do some work". If I had access to your Jonathon (and knew about him), > I would probably tell him to > do the work, rather than tell my Jonathon to do it. Any code that you create, I should be consuming as a service, not inline as a simple method. I understand the lazy, no restart benefit (up until a month ago I was developing on a sub Ghz machine and that took about 5 minutes to restart, now I'm down to 13 seconds :) ) however, as you allude to in the rest of your post by the time something is polished enough to do real work it should be in a service structure.
