Date: Tue, 19 Mar 2024 11:37:30 +0000 (UTC) Message-ID: <283472376.56499.1710848250784@cwiki-he-fi.apache.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_56498_1589777245.1710848250783" ------=_Part_56498_1589777245.1710848250783 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This page contains a summary of the ideas planned for the camel-3.0.0 release.
See CAMEL-6029.
No matter what choices and changes we make in the core, many tests in co= mponents will start failing. That is because virtually all unit tests in co= mponents test much more than the component itself, by setting up routes, et= c. A simple thing would be do create something like xyzTestSupport (where x= yz in {"Component", "Configuration", "Endpoint", "Producer", "Consumer", "L= anguage", etc... }), that test a respective area without setting up routes = and possibly use a minimal CamelContext (w/o component discover and/or othe= r features). Moving component unit tests to such a framework is not complic= ated, a bit tedious, but hopefully we'll benefit (yet again) from community= contributions and gain new committers in the process. This is probably the= first thing that should be done that will allow us to be more productive w= ith the other improvements. It can also be done in 2.x and won't require an= y incompatible changes.
See CAMEL-6076
In favor of the xxx options in our URI, we should remove the duplicated = xxxRef options from our components. This make our code and documentation mo= re lean. We should deprecate it as soon as possible and remove it in Camel = 3.0.
See CAMEL-6077
Instead of having both uri and ref for endpoints, we should unify this a= nd only use uri. If people want to use ref, then they can do that using "re= f:xx" as an uri. This would simplify code as we don't have to check for eit= her one.
See Came= l 3.0 - Message Store.