[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [smila-user] Invocation of pipelet error
|
Hi,
Am 14.05.2012 12:58, schrieb Nick:
> Hi Jürgen,
>
> thank you for the reply,
>
> actually the bundle is in the launch configuration and all the
> required bundles are added too.
> Checking in the log I found this:
>
> 2012-05-14 12:41:36,278 INFO [Component Resolve Thread (Bundle
> 90) ] management.ManagementRegistration -
> [Management Registration] Registering new agent
> [Processing/Pipelet/FrameMatchingPipeline/FrameMatchingPipelet@37
> (eu.cubrikprj.pipelet.polmi.FrameMatching.FrameMatchingPipelet)]
> 2012-05-14 12:41:36,278 INFO [Component Resolve Thread (Bundle
> 90) ] activities.PipeletManager -
> FrameMatchingPipeline/FrameMatchingPipelet@37: found pipelet
> eu.cubrikprj.pipelet.polmi.FrameMatching.FrameMatchingPipelet,
> processing request -> request
> 2012-05-14 12:41:36,278 INFO [Component Resolve Thread (Bundle
> 90) ] activities.PipeletManager -
> FrameMatchingPipeline/FrameMatchingPipelet@37: pipelet configuration
> parsed.
>
> It seems that the pipelet has been found.
>
No, these messages are just about parsing the <invokePipelet> element in
BPEL. If your pipelet class has been found, there should be a line like
this in the log file:
2012-02-13 16:38:21,047 INFO [Component Resolve Thread (Bundle
46) ] activities.PipeletManager - Pipelets
have been added:
[eu.cubrikprj.pipelet.polmi.FrameMatching.FrameMatchingPipelet, ...]
Only then will the pipelet class be available to the pipeline processor.
Otherwise there should be a log message about "Pipelet class
eu.cubrikprj.pipelet.polmi.FrameMatching.FrameMatchingPipelet could not
be loaded from bundle ..." (logged by PipeletTrackerImpl), which
hopefully gives more details, or the bundle was not found at all.
Regards,
Jürgen.