Hi Scott,
the javaflow class is loaded by the special classloader, that also loads
other classes if needed, but should not touch them if they don't
implement Continuable; however it analyze the flow class itself, and
during this phase it traverse also the TestMe class. Anyway, this is
really weird.
Thank you,
The example I provided used No inner classes, the TestMe class was just
a standard object, nothing special and the flow class was as simple as I
could make it.
My current theory is that it is some load time issue. The TestMe class
that i gave earlier is only used by the flow scrip
Hi Scott,
I'm using javaflow which calls backend objects having static variables
(for example, enumerations), and didn't incurred in this problem.
I can't understand, are you using inner classes? In that case that's the
problem. Javaflow is limited in its class handling capacities, inner
classes c
I am expeirementing JavaFlow and it seems to me to be so much of a
better fit for our needs than javascript. However in trying to implement
it I hook it into my backend I am recieving errors which are close to
the example provided but I've found that any class which is used by a
javaflow class
Hi Torsten,
thanks for your reply. I was just seeing what I could and couldn't do
with java flow classes. I stmbled across this one by accident to be
honest. Like you say, it should work!
AndrewOn 3/21/06, Torsten Curdt <[EMAIL PROTECTED]> wrote:
On 21.03.2006, at 20:26, Andrew Madu wrote:> Hi,> c
On 21.03.2006, at 20:26, Andrew Madu wrote:
Hi,
can someone please tell me why defining a class variable in a
javaflow class like so:
public class Login extends AbstractContinuable
{
static User userGlobal = new User();
.
would cause the following error to be generated?:
Hi,
can someone please tell me why defining a class variable in a javaflow class like so:
public class Login extends AbstractContinuable
{
static User userGlobal = new User();
.
would cause the following error to be generated?:
Instruction INVOKEVIRTUAL constraint violated