On Nov 21, 2012, at 1:45 AM, Babak Vahdat <babak.vah...@swissonline.ch> wrote:
> I was *not* looking for any +1 but only wanted to *make sure* that there's
> *no* good reason I'm missing here why there're *tons* of this call. So that
> I though I should better ask other experienced riders before I start
> removing (almost) all of those 226 calls!
The only thing I can think of (and we do need this in CXF) is if you need a
full URL/URI for the file for some reason. In CXF this is usually to get the
complete URL to a base WSDL so all the imports/includes and binding files and
such will work. This likely doesn't affect 95% (or higher) of the 226
calls you mentioned.
Dan
>
> ~/dev/workspace/camel>find . -name *Test.java -exec grep "getAbsoluteFile()"
> {} \; | wc
> 226 1034 15850
>
> Babak
>
>
> hadrian wrote
>> Unfortunately, it won't save any testing time as this is just a teeny,
>> tiny drop in the bucket, but it's a bit ugly.
>>
>> Babak, you don't need a bunch of +1s, just go ahead and fix it :).
>>
>> Thanks,
>> Hadrian
>>
>> On 11/20/2012 08:07 PM, Willem jiang wrote:
>>> +1 to remove that to save us some testing time :)
>>>
>
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Any-good-reason-why-make-use-of-the-java-io-File-getAbsoluteFile-API-inside-the-unit-tests-tp5722995p5723042.html
> Sent from the Camel Development mailing list archive at Nabble.com.
--
Daniel Kulp
dk...@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
