Yes, a bunch of tests fail trying to figure out what 'localhost' means :).

Caused by: java.net.UnknownHostException: unknown host
        at org.xbill.DNS.Address.lookupHostName(Address.java:239)
        at org.xbill.DNS.Address.getByName(Address.java:264)
        at 
org.apache.camel.component.dns.DnsIpEndpoint$1.process(DnsIpEndpoint.java:47)

Hadrian


On Apr 4, 2011, at 11:37 PM, Johan Edstrom wrote:

> Testing wise?
> I think I disabled all tests that would require a recursive resolver.
> 
> 
> On Apr 4, 2011, at 9:33 PM, Hadrian Zbarcea wrote:
> 
>> It also looks like the camel-dns component has some issues with my machine :(
>> 
>> Hadrian
>> 
>> 
>> On Apr 4, 2011, at 11:14 PM, Johan Edstrom wrote:
>> 
>>> Actually, were is the difficulty in supporting both?
>>> Asking as a complete ignoramus that has swapped quite a few projects, 
>>> if we follow CXF conventions and respect bus creation I do not see where 
>>> it'll be that hard?
>>> 
>>> 
>>> 
>>> 
>>> On Apr 4, 2011, at 9:09 PM, Hadrian Zbarcea wrote:
>>> 
>>>> We don't need to support cxf 2.3.x and 2.4.x at the same time. The current 
>>>> camel-2.7.0 release does not support cxf 2.4.x at all now, because of the 
>>>> following line in <camel.osgi.import.defaults>:
>>>> org.apache.cxf.*;version="[2.3.2,2.4)"
>>>> 
>>>> Hadrian
>>>> 
>>>> 
>>>> 
>>>> On Apr 4, 2011, at 10:00 PM, Willem Jiang wrote:
>>>> 
>>>>> It could be no easy to support CXF 2.3.x and CXF 2.4.x at same time by 
>>>>> reference the CXF feature in apache-camel feature. You have to deal with 
>>>>> the repo reference url and CXF vesion in the apache-camel feature.
>>>>> 
>>>>> In most case, the container which provides the runtime of camel and cxf 
>>>>> does the align job itself.
>>>>> 
>>>>> Willem
>>>>> 
>>>>> On 4/4/11 10:40 PM, Jean-Baptiste Onofré wrote:
>>>>>> OK,
>>>>>> 
>>>>>> sorry I have misunderstood you.
>>>>>> 
>>>>>> Sure, we can review the camel features descriptor to align camel and cxf
>>>>>> ones. It makes sense to reference the CXF features in camel-cxf one.
>>>>>> 
>>>>>> Regards
>>>>>> JB
>>>>>> 
>>>>>> On 04/04/2011 04:32 PM, Christian Schneider wrote:
>>>>>>> Yes we need a new camel release to be compatible with cxf 2.4. The
>>>>>>> question is only if we can also do something with the feature file to
>>>>>>> make it compatible with cxf 2.3 and 2.4.
>>>>>>> 
>>>>>>> Christian
>>>>>>> 
>>>>>>> 
>>>>>>> Am 04.04.2011 16:24, schrieb Jean-Baptiste Onofré:
>>>>>>>> Hi Christian,
>>>>>>>> 
>>>>>>>> I guess that the camel-cxf POM should be also updated to update the
>>>>>>>> CXF version range.
>>>>>>>> So we need a new Camel release for that, no ?
>>>>>>>> 
>>>>>>>> Regards
>>>>>>>> JB
>>>>>>>> 
>>>>>>>> On 04/04/2011 04:25 PM, Christian Schneider wrote:
>>>>>>>>> What do we do with the karaf feature file?
>>>>>>>>> The camel-cxf features are not suitable for cxf 2.4. On the other hand
>>>>>>>>> CXF 2.4 brings it´s own feature file. So if the cxf feature is
>>>>>>>>> installed
>>>>>>>>> camel-cxf can just be installed.
>>>>>>>>> 
>>>>>>>>> Any ideas?
>>>>>>>>> 
>>>>>>>>> Christian
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> Am 04.04.2011 16:20, schrieb Hadrian Zbarcea:
>>>>>>>>>> Hi,
>>>>>>>>>> 
>>>>>>>>>> There are a few dependencies that are used with camel that we don't
>>>>>>>>>> support as mentioned on the SMX mailing list and CAMEL-3830.
>>>>>>>>>> 
>>>>>>>>>> I think we should support at least:
>>>>>>>>>> * slf4j 1.6.x
>>>>>>>>>> * jetty 7.3.1.v20110307
>>>>>>>>>> * cxf 2.4.x
>>>>>>>>>> * (if you know of other dependencies that should be upgraded, please
>>>>>>>>>> comment)
>>>>>>>>>> 
>>>>>>>>>> ... and issue a camel-2.7.1 asap. Thoughts?
>>>>>>>>>> 
>>>>>>>>>> Hadrian
>>>>>>>>> 
>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>>>> 
>>>>> -- 
>>>>> Willem
>>>>> ----------------------------------
>>>>> FuseSource
>>>>> Web: http://www.fusesource.com
>>>>> Blog:    http://willemjiang.blogspot.com (English)
>>>>>     http://jnn.javaeye.com (Chinese)
>>>>> Twitter: willemjiang
>>>>> 
>>>>> Connect at CamelOne May 24-26
>>>>> The Open Source Integration Conference
>>>>> http://camelone.com
>>>> 
>>> 
>> 
> 

Reply via email to