ode-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthieu Riou" <matthieu.r...@gmail.com>
Subject Re: Ode Logging, Management API, and JBI
Date Thu, 26 Jul 2007 16:12:45 GMT
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 <leutnant.dan@gmail.com> 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 <matthieu.riou@gmail.com> wrote:
> >
> > On 7/21/07, Tammo van Lessen <tvanlessen@gmail.com> wrote:
> > >
> > > 2007/7/20, Alex Boisvert <boisvert@intalio.com>:
> > > > 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 - tvanlessen@gmail.com - http://www.taval.de
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message