Hi Dan, First of all, thank you very much for your response! I guess I understood your proposal, but I still have one doubt. Using that solution the deployer of each service would have to include that file in the service's war file, right? I mean, I guess he must be aware of my StartupBean. In the case he doesn't remember to create the file, the service would not be monitored. Another point is that I would like to configure my chain of interceptors at runtime, and not just at deployment time. Well, I guess that at the point that you mentioned I could start an osgi runtime to support the required dynamism anyway.
Thank you, again! Best regards, Fábio On Thu, Jun 2, 2011 at 2:49 PM, Daniel Kulp <[email protected]> wrote: > > With 2.4.x, this should be pretty easy to do. If you create a > > META-INF/cxf/bus-extensions.txt > > that looks something like: > > com.my.cool.monitoring.StartupBean::false > > and that bean has a constructor that takes a Bus, when a Bus is created, it > would automatically find that bean and create it with the Bus param. You > can > then add your interceptors to the Bus directly at that point and wire in > whatever other things you need. > > Dan > > > > On Thursday, June 02, 2011 9:20:20 AM Fabio souza 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. > To > > do that, I plan to start an osgi context (that will be used to > > register my *Monitoring > > services*) when the CXF bus is started (however, I am not sure how I > could > > do that). Also, I plan to plug my chainer interceptor directly to the > bus, > > 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! > > > > > -- > Daniel Kulp > [email protected] > http://dankulp.com/blog > Talend - http://www.talend.com > -- Fábio
