Naïve use of @log would simply embedd it in an @begin @EnD block where a logging statement occurs, however, @log appears to need to follow an @out annotation, having a bare @log which happens to follow a @in statement results in a not immediately helpful exception:
java.lang.ClassCastException: org.yesworkflow.annotations.In cannot be cast to org.yesworkflow.annotations.Out
Graceful failure in this case with a pertinent error message would help.
To reproduce:
# @BEGIN FilterExcludingMarine
# @IN TaggedDataRecord
# @LOG {timestamp} [{loglevel}] ACTOR<{actorname}> -> [{filterKey}]=[{matchValue}]:{match}. Passing occurrenceID={occurrenceID}
# @OUT NotMarine
# @END FilterExcludingMarin
Naïve use of @log would simply embedd it in an @begin @EnD block where a logging statement occurs, however, @log appears to need to follow an @out annotation, having a bare @log which happens to follow a @in statement results in a not immediately helpful exception:
Graceful failure in this case with a pertinent error message would help.
To reproduce: