I'm trying to run the example but got this: Error executing command:
Unresolved constraint in bundle exchange [214]: Unable to resolve 214.0:
missing requirement [214.0] package;
(&(package=org.apache.servicemix.nmr.api)(version>=1.5.0))

On Thu, Jun 9, 2011 at 1:54 PM, Jean-Baptiste Onofré <j...@nanthrax.net>wrote:

> Hi Jie,
>
> you have an example of custom interceptor (for both endpoint and exchange),
> in the ServiceMix NMR module:
>
>
> http://svn.apache.org/repos/asf/servicemix/smx4/nmr/trunk/examples/interceptors/
>
> With that you can implement interceptor for auditing or whatever you want.
>
> regards
> JB
>
>
> On 06/09/2011 06:46 PM, Jie Lee wrote:
>
>> Hi,
>>
>> I'd like to be able to dynamically monitoring different aspects
>> related to web services (e.g. response time, processing time,
>> availability,
>> etc). I would like that the set of possible monitoring aspects was an
>> open end. I mean, I would like to be able to start monitoring something
>> that
>> wasn't planned before without stopping the service. I did something like
>> that in the context of DOSGi. In fact, I modified DOSGi  to include a
>> customized interceptor (that I call the *chainer*) when an endpoint is
>> going
>> to be published. This interceptor is notified when a new
>> *monitoring interceptor* (an osgi service) is started and plug it in the
>> corresponding chain of interceptors. In that way, the next request to this
>> service will be monitored. Well, I am considering to use the same idea out
>> of an dosgi environment (however, I am not sure how I could do that).
>> Also,
>> I plan to plug my chainer interceptor directly to the bus or, add my
>> chainer
>> interceptor into the interceptor chain of Service Mix, so that the
>> developer
>> of the services would not be necessarily aware of the monitoring stuff.
>> Could you please tell me if this idea seems to make sense? Is there some
>> particular documentation that I could use?
>>
>> Thank you, very much!
>>
>>


-- 
[]'s

Zan Jie Lee

Reply via email to