On Jul 3, 2012, at 11:04 AM, Sergey Beryozkin wrote:
> On 02/07/12 17:57, Marek Potociar wrote:
>> On Jul 2, 2012, at 5:49 PM, Bill Burke wrote:
>>
>>> Sorry, catching up after a mini-vacation with family.
>>
>> No problem. Hope you had fun.
>>
>>> We have a toString(...) for client side. Use both in our low-level, jax-rs-2.0-like client API and also within our proxy framework. Would still be useful for JAX-RS 2.0 when passing objects to WebTarget.pathParam and Webtarget.queryParam as well as when creating forms.
>>
>> Ah, seems so obvious now :) Thanks!
>
> So why would one prefer implementing StringConverter as opposed to overriding toString() ? I do not understand the case
Perhaps because you can't override toString as the class is out of your control (JDK classes, 3rd party modules...)
Marek
>
> Cheers, Sergey
>
>>
>> Marek
>>
>>>
>>> On 6/29/12 7:18 PM, Marek Potociar wrote:
>>>> Hi Bill,
>>>>
>>>> I am looking into resolving issue #61 (
>>>> http://java.net/jira/browse/JAX_RS_SPEC-61 ) and while the purpose
>>>> behind StringConverter.fromString(...) method is clear to me (we have a
>>>> very similar concept in Jersey too), I'm not clear about the purpose of
>>>> the StringConterter.toString(...) method. Is it really used? What do you
>>>> use it for?
>>>>
>>>> Right now it seems to me that the fromString part should cover the use
>>>> cases alone. Or am I missing something?
>>>>
>>>> Thanks,
>>>> Marek
>>>
>>> --
>>> Bill Burke
>>> JBoss, a division of Red Hat
>>> http://bill.burkecentral.com
>>>
>>>
>>
>
>
> --
> Sergey Beryozkin
>
> Talend Community Coders
> http://coders.talend.com/
>
> Blog: http://sberyozkin.blogspot.com