> But hardcoding workflow in any kind of java class (actions,
> beans, even special
> classes just dedicated to that)
> I wouldn't recommend it for mantainability's sake.
> Just another 2c,
> Dan
Ah. Thanks for the insight. The reason why I'm focused on the hardcoded
links is that I need to
Ahhh. Interesting discussion! Let me add some opinion also.
> -Ursprüngliche Nachricht-
> Von: Daniel Lopez [mailto:[EMAIL PROTECTED]]
> Gesendet am: Freitag, 14. April 2000 15:41
> An: [EMAIL PROTECTED]
> Betreff: Re: Model 2 and multi-page techniques
>
> Hi,
>
> I'll add some comments
I tried using environment variables because the webserver that hosts my
website doesn't feature servlets yet. But I have not succeeded. It seems
that by deprecating the getenv() calls and suggesting property files, SUN
wants to prevent the usage of environment variables completely: either type
it
To continue the navigation discussion of a few days back involving property
files, may I provide an alternate option? I'll try doing this based on an
simplified example:
Suppose there are two simplified workflows that share the same pages. For
example: the first page enters a number A, the second
a) only limited by the memory of the running system or better the
addressable memory from within the JVM.
b) out of memory exception for the "new". If an actual out of memory for the
JVM occurs, it will crash (since it is just another process)
-Ursprüngliche Nachricht-
Von: Sachin S. K
