Hi,
On 31/10/12 10:46, Sergey Beryozkin wrote:
Hi
On 31/10/12 10:16, Dennis Kieselhorst wrote:
Hi,
I'm looking for a sample implementing a ParamConverterProvider. What's
good practice? Simply matching on raw type and returning an appropriate
ParamConverter instance? I also dipped into the JSR-339 public review
spec but found nothing about that.
The only example I have is in the implementation code (ProviderFactory)
itself, the legacy ParameterHandlers are wrapped within
ParamConverterProvider and ParamConverter pairs. I'm going to work on
the documentation in the next few days for all the new features.
I should say I was not too optimistic about introducing a pair of
interfaces but it is going to stay, I'd say the way to work with them is
to have ParamConverterProvider with a map of ParamConverters initialized
early, and then just use a ParamConverterProvider rawType parameter as a
key
Compared to the deprecated CXF-specific ParameterHandler approach, the
standardized ParamConverter also contains a toString method. I would
expect that I can use the ParamConverter on the client side to get
complex objects automatically transformed when using them as parameter.
You are right
How to apply the ParamConverterProvider to the WebClient?
I did not manage to do it in time for 2.7.0, but definitely will be
done, will try for 2.7.1, given that WebClient is expected to support
all the new extensions
I've prototyped the initial support for it on the client side, can you
please experiment with 2.7.1-SNAPSHOT ? Register the custom
ParamConverterProvider as provider with WebClient, and it should work
for path, matrix, queries, headers
thanks, Sergey
Regards
Dennis
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Blog: http://sberyozkin.blogspot.com
