Thanks, very useful. Cheers.
Michael Quilleash Morgan Stanley | Technology 20 Cabot Square | Canary Wharf | Floor 01 London, E14 4QW Phone: +44 20 7677-4543 [EMAIL PROTECTED] -----Original Message----- From: Daniel Kulp [mailto:[EMAIL PROTECTED] Sent: 22 September 2008 14:46 To: [email protected] Cc: Quilleash, Michael (IT) Subject: Re: Application "scope" in CXF There's a BUNCH of options in CXF to accomplish this. The exchange holds the BindingOperationInfo (exchange.get(BindingOperationInfo.class)) as well as the EndpointInfo and some other. Any of those are "property" holders that can store anything you want. Obviously, they are all endpoint specific locations. The Bus, while not a property holder (although it should be. Dan D. said he was going to make it one at one point, I guess he never got around to it), can store various extension objects by class. You could have a "MyDataRegistry" class and store that on the bus: bus.setExtension(reg, MyDataRegistry.class); and then query it later with: bus.getExtension(MyDataRegistry.class); The bus is in the exchange as well: exchange.get(Bus.class); Dan On Monday 22 September 2008 7:14:57 am Quilleash, Michael (IT) wrote: > Hi all, > > I am looking for a fairly wide "scope" in a CXF app that I can store > something in. > > My particular case I want to keep track of in progress requests and > information about them so if a request is taking a long time we can > send a request to the server to get the information out. The Exchange > is per request but I was wondering if there's like an application-type > scope or something similar? > > Cheers. > > Michael Quilleash > Morgan Stanley | Technology > 20 Cabot Square | Canary Wharf | Floor 01 London, E14 4QW > Phone: +44 20 7677-4543 > [EMAIL PROTECTED]<mailto:[EMAIL PROTECTED] >com> -------------------------------------------------------- > > NOTICE: If received in error, please destroy and notify sender. Sender does > not intend to waive confidentiality or privilege. Use of this email is > prohibited when received in error. -- Daniel Kulp [EMAIL PROTECTED] http://www.dankulp.com/blog -------------------------------------------------------- NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error.
