on 6/18/01 2:47 PM, "Gary Lawrence Murphy" <[EMAIL PROTECTED]> wrote:
> "Never" is a big use-space ;) It's more accurate to say that Turbine
> may _repeatedly_ suggest alternate ways using sometimes obtuse cues:
>
> For example, if I foolishly assume all RunData manipulations I do in
> MySessionValidator are valid, Turbine of course allows them, but
> throws up the runtime exception "Screen not found" --- what it meant
> to say was that it is useless to setScreen inside sessionValidator
> because it will be cleared later in the Turbine.java ... the correct
> way is getProperties().setString("screen",...) which is only obvious
> if you know about the property key.
>
> Of course, the Source tells us so, but some of these context are
> more obscure, for example, when I was trying to find how the login
> screen kept loading DefaultLayout whereas ever config instance was
> clearly MyLayout. The answer was deep in the Flux.
>
> When dealing with opaque references, it might save some questions if
> we follow a convention of stating in the JavaDocs where methods alter
> any global or session-scoped data; the first point of study for Java
> is generally through the API docs or, later, through a combination of
> looking at one source file while viewing the API docs for the next
> deeper level. API docs are always the first probe; if what we do works
> as expected, we generally don't go any further -- after all, few of us
> _really_ know how java.net.URLConnection _really_ works (those who do
> don't use it ;)
Great suggestions! I eagerly await your documentation. :-)
:-)
-jon
--
"Open source is not available to commercial companies."
-Steve Ballmer, CEO Microsoft
<http://www.suntimes.com/output/tech/cst-fin-micro01.html>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
