Our policy is that putting business logic in the flowscript is to beIs the debbuging improvement worth the effort of translation? I do my bussiness logic as an Avalon Component, and I call the component from the sitemap when needed.. I find it a little bit hard to debug, but keeps the code clean and concerns as separate as I need them.
considered OK in a prototyping stage. Once the prototype is tested, you
should reimplement it in a Java method or class. Of course, this takes
discipline and sometimes the move-to-Java stage can be postponed (or
forgotten) due to deadline pressure, as always.
Translating from Javascript to Java is quite easy, given that:
- the two languages are quite similar, syntactically
- we have no real JS experience and thus tend to use it like Java, without using its peculiar features
- we tend to switch to Java as soon as the complexity of a flowscript increases.
Ugo
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
