On 14/05/13 06:54, arjjun dhar wrote:
Problem was solved and I was also now able to upgrade.
The following notes applied to this problem...
1. ParameterHandlers are the lowest grade citizens for param mapping and it
can be frustrating to figure out what else is getting in the way before it
reaches the Handler; if multiple providers are provided and one is
leveraging some common aspects between the providers. ..Example: The
provider TYPE's are very similar only subtly different.
FYI, in CXF 2.8.0, where CXF specific ParameterHandlers have actually
been removed, the JAX-RS 2.0 ParameterConverters will be checked first,
before the default mechanism of converting various URI parts into
parameters is used.
2. While the documentation states one can have the same class implement both
MessageBodyReaders and ParameterHandlers, it can lead to a lot of trouble.
Its possible but better avoidable .. infact I think it should be discouraged
(personal opinion for keeping a simpler cleaner design).
Well, I'm fine with your preferring not to have a single handler class
implementing both MessageBodyReader & ParameterHandler, just note that
MessageBodyReader & ParameterHandler deal with completely different
parts of the request, so while keeping the implementations separately
may indeed be a good idea having a combined implementation has to work
as if it were 2 different implementations
... as a result, Im giving up the use of ParameterHandler and its got me a
cleaner predictable design/code now and it all works without any magic.
Yes, having simple parameter types indeed makes things simpler
Cheers, Sergey
Thanks for all your help.
--
View this message in context:
http://cxf.547215.n5.nabble.com/jaxrs-providers-not-respected-when-migrating-from-2-5-2-to-2-7-x-tp5723630p5727623.html
Sent from the cxf-user mailing list archive at Nabble.com.
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Blog: http://sberyozkin.blogspot.com
