Hi Perhaps the most straightforward advice is to use HTTP headers instead. SOAP headers are often used for some out-of-band information be transferred across multiple hops, with some of them using alternative transports - so if it is HTTP only then may be you can use HTTP headers. RESTful applications are often more fine-grained - every significant resource can be individually linked to - perhaps it might make sense, in some case, to introduce a dedicated resource dealing with the audit information.
cheers, Sergey Nathaniel Auvil wrote: > > I have been a SOAP user for the past several years and am trying to create > a > RESTful style architecture for the first time. What is a best practice or > "good" way to pass things like Source System Id and other audit type > information? IN SOAP, I would use the SOAP Header and i am thinking i do > not want to pollute my entities with extra info. Any advice or ideas > would > be greatly appreciated. > > -- View this message in context: http://www.nabble.com/RESTful-advice-tp24227149p24245586.html Sent from the cxf-user mailing list archive at Nabble.com.
