Mmm - seems still to be there (on SendDefinition). I'm deriving a class from WireTapDefinition - which can no longer find getUriOrRef() moving from camel 2.7 to 2.8 :) On 8 Sep 2011, at 11:59, Rob Davies wrote:
> getUriOrRef() was removed from ProcessDefinition between Camel 2.7 and Camel > 2.8 (not even deprecated) - what's the thinking behind that ? > > thanks, > > Rob > > On 6 Sep 2011, at 12:36, Christian Schneider wrote: > >> Btw. I just compiled the unchanged camel-extra components against my current >> camel trunk and they showed no compile or test failures. >> So I hope we can fix the problem you see quite fast. >> >> Christian >> >> >> Am 06.09.2011 12:50, schrieb Christian Schneider: >>> Hi bvahdat, >>> >>> this is important feedback. Can you give me the compile failures. I will >>> make sure this will be compatible. >>> We are currently at a snapshot. So stuff is not in release quality. Btw. >>> this is why I would like to do a release candidate. >>> It is great you already tested this but many people will only do this with >>> some "official" release. >>> >>> Christian >>> >>> >>> Am 06.09.2011 08:06, schrieb bvahdat: >>>> Hi All, >>>> >>>> the use-case Claus gave as an example in his last post indeed happened >>>> today >>>> morning with my client to whom I've provided the application (running >>>> stable >>>> since July 27th with camel 2.8.0 in the production). >>>> >>>> I wanted to give a try to the snapshot build of today morning at [1], and >>>> following what I see: >>>> >>>> - The code doesn't even compile, and maven-compile-plugin fails (while >>>> doing >>>> 'mvn install') with a bunch of compilation errors, however I didn't have >>>> time enough to see where/why these happen. I'll dig into it later. >>>> >>>> - And there're 14 test cases now suddenly failing, mostly by the own >>>> component (zls) which does logging of different events to the >>>> central-logging-system of the client as the payloads pass through different >>>> endpoints (camel-jms, camel-jpa, camel-spring-ws, etc.), which at the same >>>> time is used for Auditing of the client applications. >>>> >>>> So at least to me this refactoring hysterie was not as smooth as it was >>>> claimed to be. Being a camel user in the last 10 months was really a great >>>> fun to me... And it's a pity to see what's going on by the camel community >>>> today! >>>> >>>> Regards, Babak >>>> >>>> [1] >>>> https://repository.apache.org/content/repositories/snapshots/org/apache/camel/camel/2.9-SNAPSHOT/ >>>> >>>> >>>> -- >>>> View this message in context: >>>> http://camel.465427.n5.nabble.com/DISCUSS-API-stability-in-Camel-2-x-tp4770632p4773307.html >>>> Sent from the Camel Development mailing list archive at Nabble.com. >>>> >>> >>> >> >> >> -- >> -- >> Christian Schneider >> http://www.liquid-reality.de >> >> Open Source Architect >> Talend Application Integration Division http://www.talend.com >> >
