Same problem happens with onAlarm in pick.
| pick
| onAlarm for='PT5S'
| empty/
| /onAlarm
| /pick
| pick
| onAlarm for='PT5S'
| empty/
| /onAlarm
| /pick
| invoke ? /
|
It works.
Alex, I did use escaped strings quot;, gt; and lt; for the
double-quote character (), the right angle bracket () and the left angle
bracket (), respectively, in my testing. I don't know why they are changed to
their literal form, even I Previewed them to make sure they were escaped
strings
Sorry for causing the confusion.
Let me make it simple: (in my test, the invoke itself is very fast and takes
much less than 1 second)
First, 1 wait activity
| wait for='PT5S' /
| invoke ? /
|
or
| invoke ? /
| wait for='PT5S' /
|
They work.
Second, 2 wait activities
|
No. I mean 60 MINUTES. Actually, PT60M8S to be exact, and the result delay was
3608 seconds.
As of the weird issue :-(
The pulling interval is 1 second:
| !-- jBPM Scheduler --
| servlet
| servlet-nameschedulerServlet/servlet-name
|
I try to assign some special characters as input value, for example
assign
| copy
| from expression='-?/='/
| to variable=inputVariable/
| /copy
| /assign
it works and I got anonymous wrote : -?/= as the result.
But when I
Alex, thanks. Now I tested wait up to PT60M and it worked.
But I encountered another problem: it does NOT work when I put a wait before
and a wait after an invoke of a partnerLink, for example
wait for='PT5S' /
invoke name=Invoke_eOffer partnerLink=PartnerLink_eOffer
portType=ns4:SwsService
I'm using wait activity like
wait for='PT10S' /
The actual ELAPSE time varies at each run, from 10 seconds to 120 seconds.
When I used
wait for='PT30S' /
The actual ELAPSE time ranged from 30 seconds to 120 seconds from multiple
runs. Some runs just timed
