Ok so the exception was really a classloading issue for your listener. Now
could you check that during startup, if you set your debug level to INFO,
you get the following trace:

Registered custom BPEL event listener: foo

Thanks,
Matthieu

On 3/28/07, wolfgang10 <[EMAIL PROTECTED]> wrote:


If I put the jar with my Listener in the
data/smx/components/OdeBpelEngine/version_1/lib directory the error
disappears. But it is never called during the execution of a process.

Wolfgang


Matthieu Riou-2 wrote:
>
> This class must definitely be in ODE's classpath so I would think that
> it's
> actually missing in your listener's classloader. So where did you place
> your
> listener implementation? I'm not sure how ServiceMix isolates its
> different
> classloaders so to start with I would try putting your listener right
with
> the other ODE libraries in the service assembly.
>
> Alternatively you can try to drop it in the ServiceMix work directory
> under
> data/smx/components/OdeBpelEngine/version_1/lib.
>
> Cheers,
> Matthieu
>
> On 3/28/07, wolfgang10 <[EMAIL PROTECTED]> wrote:
>>
>>
>> I now get:
>>
>> Exception in thread "Timer-4" java.lang.NoClassDefFoundError:
>> org/apache/ode/bpel/iapi/BpelEventListener
>>         at java.lang.ClassLoader.defineClass1(Native Method)
>>         at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
>>         at
>> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
>>         at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
>>         at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
>>         at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
>>         at java.security.AccessController.doPrivileged(Native Method)
>>         at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
>>         at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
>>         at
>> org.codehaus.classworlds.RealmClassLoader.loadClassDirect(
>> RealmClassLoader.java:195)
>>         at
>> org.codehaus.classworlds.DefaultClassRealm.loadClassDirect(
>> DefaultClassRealm.java:412)
>>         at
>> org.codehaus.classworlds.DefaultClassRealm.loadClass(
>> DefaultClassRealm.java:376)
>>         at
>> org.codehaus.classworlds.RealmClassLoader.loadClass(
RealmClassLoader.java
>> :214)
>>         at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
>>         at
>> org.apache.xbean.classloader.MultiParentClassLoader.loadClass(
>> MultiParentClassLoader.java:184)
>>         at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
>>         at java.lang.ClassLoader.loadClassInternal(ClassLoader.java
:319)
>>         at java.lang.Class.forName0(Native Method)
>>         at java.lang.Class.forName(Class.java:164)
>>         at
>> org.apache.ode.jbi.OdeLifeCycle.registerEventListeners(
OdeLifeCycle.java
>> :260)
>>         at org.apache.ode.jbi.OdeLifeCycle.init(OdeLifeCycle.java:109)
>>         at
>> org.apache.servicemix.jbi.framework.ComponentMBeanImpl.init(
>> ComponentMBeanImpl.java:201)
>>         at
>> org.apache.servicemix.jbi.framework.ComponentMBeanImpl.doStart(
>> ComponentMBeanImpl.java:287)
>>         at
>> org.apache.servicemix.jbi.framework.ComponentMBeanImpl.start(
>> ComponentMBeanImpl.java:216)
>>         at
>> org.apache.servicemix.jbi.framework.InstallationService.install(
>> InstallationService.java:331)
>>         at
>> org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive
(
>> AutoDeploymentService.java:276)
>>         at
>>
org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDirectory
>> (AutoDeploymentService.java:645)
>>         at
>> org.apache.servicemix.jbi.framework.AutoDeploymentService.access$200(
>> AutoDeploymentService.java:62)
>>         at
>> org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(
>> AutoDeploymentService.java:605)
>>         at java.util.TimerThread.mainLoop(Timer.java:512)
>>         at java.util.TimerThread.run(Timer.java:462)
>>
>>
>>
>>
>> Matthieu Riou-2 wrote:
>> >
>> > Yep, apparently the listeners weren't registered by the jbi module
>> (only
>> > Axis2). I just fixed that, can you try again?
>> >
>> > Thanks,
>> > Matthieu
>> >
>> > On 3/28/07, wolfgang10 <[EMAIL PROTECTED]> wrote:
>> >>
>> >>
>> >> I tried to add my listener to ode-jbi.properties without any effect.
>> >>
>> >> ode-jbi.event.listeners=tracking.OdeListener
>> >>
>> >> Any idea what might be the reason?
>> >> Wolfgang
>> >>
>> >>
>> >> Alex Boisvert wrote:
>> >> >
>> >> > With the JBI integration layer, this file is called
>> ode-jbi.properties
>> >> >
>> >> >
>> >> > On 3/27/07, wolfgang10 <[EMAIL PROTECTED]> wrote:
>> >> >>
>> >> >>
>> >> >> I´m using ode-jbi. Where can I find ode-axis2.properties?
>> >> >> Wolfgang
>> >> >>
>> >> >>
>> >> >> Alex Boisvert wrote:
>> >> >> >
>> >> >> > See
>> >> >> >
>> >> >>
>> >>
>>
http://incubator.apache.org/ode/user-guide.html#UserGuide-ODEExecutionEvents
>> >> >> >
>> >> >> >
>> >> >> > On 3/27/07, wolfgang10 <[EMAIL PROTECTED]> wrote:
>> >> >> >>
>> >> >> >>
>> >> >> >> Is there a way to track processes as they are executed?
>> >> >> >> Something like a callback listener that is registered and
called
>> >> every
>> >> >> >> time
>> >> >> >> an activity is being processed?
>> >> >> >>
>> >> >> >> Wolfgang
>> >> >> >> --
>> >> >> >> View this message in context:
>> >> >> >> http://www.nabble.com/Tracking-tf3474697.html#a9698014
>> >> >> >> Sent from the Apache Ode User mailing list archive at
>> Nabble.com.
>> >> >> >>
>> >> >> >>
>> >> >> >
>> >> >> >
>> >> >>
>> >> >> --
>> >> >> View this message in context:
>> >> >> http://www.nabble.com/Tracking-tf3474697.html#a9699119
>> >> >> Sent from the Apache Ode User mailing list archive at Nabble.com.
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >>
>> >> --
>> >> View this message in context:
>> >> http://www.nabble.com/Tracking-tf3474697.html#a9715659
>> >> Sent from the Apache Ode User mailing list archive at Nabble.com.
>> >>
>> >>
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Tracking-tf3474697.html#a9716926
>> Sent from the Apache Ode User mailing list archive at Nabble.com.
>>
>>
>
>

--
View this message in context:
http://www.nabble.com/Tracking-tf3474697.html#a9717715
Sent from the Apache Ode User mailing list archive at Nabble.com.


Reply via email to