Thanks Ian, seems like the best approach. 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: Ian Roberts [mailto:[EMAIL PROTECTED] Sent: 21 September 2008 13:42 To: [email protected] Subject: Re: "Around" interceptor Quilleash, Michael (IT) wrote: > Thanks for the reply Ian. > > I did see this approach being used by the default interceptors, > however I found out that the out/outFault messages are always null > when the "in" interceptor is invoked so the interceptor chains aren't > available to add new interceptors to. > > I haven't found an example of any interceptors that add interceptors > to different interceptor chains. > > Is there a way of doing what you are saying, perhaps by creating the > out messages earlier? Hmm. In that case you might be better off just keeping the start and stop interceptors separate and creating a "feature" (see LoggingFeature for an example) to group them together. That way it's still a single configuration operation to add both interceptors - just add the feature to the bus, server, client, whatever. Ian -- Ian Roberts | Department of Computer Science [EMAIL PROTECTED] | University of Sheffield, UK -------------------------------------------------------- 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.
