I think a distinct activity type for custom eventing / logging might be better. It would avoid the confusion about whether the event is generated before or after the activity and avoid the generation of the event (e.g., assignment failures) from affecting the activity's execution.
alex On 7/26/07, Matthieu Riou <[EMAIL PROTECTED]> wrote: > > That's actually what I meant without writing it :-) We could add an > element > that would be nested within any activity (simple or complex) and would > fire > custom messages. That would be the BPEL extension. For the runtime it > would > just be another type of event. > > Matthieu > > On 7/26/07, Paul Brown <[EMAIL PROTECTED]> wrote: > > > > Hmmm. Does it make sense to open up the eventing facility a little > > bit and allow UserEvent or some other such to be dispatched from > > within an activity. I can see plenty of generic applications > > (BIM/BAM) for being able to notify on markers in a process, and it > > would be a shame to have parallel implementations of eventing > > subsystems when we have one for process events already... > > > > -- Paul > > > > On 7/26/07, Matthieu Riou <[EMAIL PROTECTED]> wrote: > > > Oh yes, I see what you mean now. Never thought of that but it would > > actually > > > be a nice idea for a BPEL extension. So ODE doesn't support it but if > > you or > > > somebody else is interested in it, we always welcome contributions :-) > > > > > > Cheers, > > > Matthieu > > > > > > On 7/26/07, Dan <[EMAIL PROTECTED]> wrote: > > > > > > > > Let me clarify... I'm looking for the debug messages in the "dan" > > > > namespace. :) > > > > > > > > I want to write arbitrary messages to standard i/o to debug / > analyze > > my > > > > business processes, themselves, rather than Ode. > > > > > > > > Thanks, > > > > Dan > > > > > > > > On 7/26/07, Matthieu Riou <[EMAIL PROTECTED]> wrote: > > > > > > > > > > Depends what kind of debug messages you'd be interested in but > there > > are > > > > > plenty of them in ODE that you can get simply by setting the > > > > > org.apache.odelog4j category to debug. > > > > > > > > > > Cheers, > > > > > Matthieu > > > > > > > > > > On 7/26/07, Dan < [EMAIL PROTECTED]> wrote: > > > > > > > > > > > > In lieu of (or maybe in addition to) event logging is there a > way > > to > > > > > echo > > > > > > debug messages to stdout or to the servicemix console? Like a > > bpel > > > > > printf > > > > > > statement? > > > > > > > > > > > > Thanks, > > > > > > Dan > > > > > > > > > > > > On 7/21/07, Matthieu Riou <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > > On 7/21/07, Tammo van Lessen < [EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > > > > 2007/7/20, Alex Boisvert <[EMAIL PROTECTED]>: > > > > > > > > > I think it would be nice have a BpelEventListener that > > outputs > > > > > > > > > (pretty-print) events to Log4J... any takers? > > > > > > > > > > > > > > > > I'll take care of that. I have also one implementation of > that > > > > > > > > listener that serializes the events to XML and publishes > them > > to a > > > > > JMS > > > > > > > > topic. Interested anyone? > > > > > > > > > > > > > > > > > > > > > Of course :-) > > > > > > > > > > > > > > Do you have any preferences where to put such stuff? I guess a > > new > > > > > > > > module for Ode API usage samples would be good. My proposal > is > > > > > > > > "extension-examples". What do you think? > > > > > > > > > > > > > > > > > > > > > I'd put the log4j thing in the standard module set, I think in > > > > > bpel-epr > > > > > > > (that really should be renamed bpel-common) would be the right > > > > > place. It > > > > > > > really makes sense to have that part of the normal tree (even > if > > > > > it's > > > > > > not > > > > > > > normally enabled). And then the XML over JMS implementation > > would go > > > > > in > > > > > > > the > > > > > > > extensions module. > > > > > > > > > > > > > > What do you think? > > > > > > > > > > > > > > Matthieu > > > > > > > > > > > > > > Tammo > > > > > > > > > > > > > > > > -- > > > > > > > > Tammo van Lessen - [EMAIL PROTECTED] - > http://www.taval.de > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > [EMAIL PROTECTED] > > http://mult.ifario.us/ > > >
