Hi,
Sorry for the cluttered message.
Here I go again.
Thanks for your replies.
Having a custom @Context type is too much of a work for just to avoid
extracting the auth data manually. (and I'm not sure how to do that either
:-) )
I think I know how we can do it, some vague idea came to me during my lunch break...but I'll try to get to it later on and see how
realistic it is...
_______________________
[thinking wild]
Life can become so much easier if the framework can allow "@HeaderParam
along with @Context" for instance variables.... :-)
_______________________
Yea, that's what you can do too. Unfortunately @HeaderParam are not thread safe, when injected into a field, but again let us think
a bit more what can we do in this regard...You might want to try injecting it as a beanProperty
@HeaderParam
public void setAuthorization(String value) {
AuthorizationData ad = fromString(value);
threadLocalAuthorization.put(ad);
}
it might work actually...
Cheers, Sergey
Coming back to the topic, please let me know if there is a possibility of
adding pre/post methods. (as Sergey mentioned) That will surely help my
purpose.
--
View this message in context:
http://www.nabble.com/Extracting-HTTP-authorization-header-tp22076857p22078097.html
Sent from the cxf-user mailing list archive at Nabble.com.
