Hi David,
don't know if you have set any timeouts for your tests such as
+) Email.MAIL_SMTP_CONNECTIONTIMEOUT
+) Email.MAIL_SMTP_TIMEOUT
+) Email.setSocketConnectionTimeout()
+) Email.setSocketTimeout()
The first two go into the email session for (javax.mail) while the two
others are set
Hi everyone,
I'm starting using SCXML and there is something that I am not sure to
understand very well. In the previous applications I developed, I used an
event-driven architecture : my user interface (for instance) was triggering
Events that an EventDispatcher converted into (a) Action
On Fri, Aug 20, 2010 at 3:06 PM, Christopher Dragert
chris.drag...@mail.mcgill.ca wrote:
My SCXML is crashing when I try to run it and my debugging efforts have gone
for naught. The observable behaviour is as follows -- from the state
stationary, the state machine checks the guard on a
2010/8/21 Thiébault Benoît d...@artenum.com:
Hi everyone,
I'm starting using SCXML and there is something that I am not sure to
understand very well. In the previous applications I developed, I used an
event-driven architecture : my user interface (for instance) was triggering
Events that
Thanks for the reply Siegfried.
I did not have any timeout settings for my test. But it looks like these
settings are available only in 1.3 dev, not the release build (I'm using
1.2).
I didn't quite follow how to make use of the first two options
(MAIL_SMTP_CONNECTIONTIMEOUT/TIMEOUT).
But in
Oh what a bugger, I see these two options are available in 1.2, but the
javadocs on the website are out of date (they don't show these two options).
And yep, that's what I needed to fix the problem. I'll put in a patch
suggestion to set these to default values out of the box. We definitely
Hi,
Thanks for the response. It was in fact just sitting 'silent'. There were no
events being supplied so the conditions were never being checked. I set up a
heartbeat type eventand this solved the problem.
Regards,
Chris Dragert
From: Rahul Akolkar
