You need to update the camel-core version at the same time :)
Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Tue, Jun 19, 2018 at 9:44 PM, Binole, William J < william.j.bin...@questdiagnostics.com> wrote: > Willem thank you for your response. Yes, all the jars were updated at the > same time and all have 2.21.1 in their names. Dependencies from the pom > are listed below. > > <dependency> > <groupId>org.apache.camel</groupId> > <artifactId>camel-core</artifactId> > <version>2.19.5</version> > </dependency> > > <dependency> > <groupId>org.apache.camel</groupId> > <artifactId>camel-mina2</artifactId> > <version>2.21.1</version> > <!-- use the same version as your Camel core version --> > </dependency> > > <dependency> > <groupId>org.apache.camel</groupId> > <artifactId>camel-ftp</artifactId> > <version>2.21.1</version> <!-- was 2.1.0, but jsch dependency > breaks --> > </dependency> > > <dependency> > <groupId>org.apache.camel</groupId> > <artifactId>camel-hl7</artifactId> > <version>2.21.1</version> <!-- was 2.1.0, but hapi 0.5.1 > dependency breaks --> > </dependency> > > <dependency> > <groupId>org.apache.camel</groupId> > <artifactId>camel-http-common</artifactId> > <version>2.21.1</version> > </dependency> > > <dependency> > <groupId>org.apache.camel</groupId> > <artifactId>camel-http</artifactId> > <version>2.21.1</version> > </dependency> > > > > <dependency> > <groupId>org.apache.camel</groupId> > <artifactId>camel-jms</artifactId> > <version>2.21.1</version> > </dependency> > > <dependency> > <groupId>org.apache.camel</groupId> > <artifactId>camel-spring</artifactId> > <version>2.21.1</version> > </dependency> > > -----Original Message----- > From: Willem Jiang [mailto:willem.ji...@gmail.com] > Sent: Tuesday, June 19, 2018 12:28 AM > To: users@camel.apache.org > Subject: Re: Camel 2.21.1 HttpComponent > > CAUTION: This email originated from outside of the organization. Do not > click links or open attachments unless you recognize the sender and know > the content is safe. > > > The registerExtension method is provided by camel-core. > Please check if you updated the camel-core jar at the same time. > > As the major version upgrade could introduce internal API change. We don't > suggest user just upgrade the version of camel-component unless it's a > patch release, such as 2.19.4 -> 2.19.5. > > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Tue, Jun 19, 2018 at 5:24 AM, Binole, William J < William.J.Binole@ > questdiagnostics.com> wrote: > > > We recently upgraded our camel libs to the latest version (2.21.1) and > > have found that we can no longer instantiate HttpComponent. This is > > due to the constructor calling the registerExetnsion method which we > > have yet to find in the source. > > > > public HttpComponent(Class<? extends HttpEndpoint> endpointClass) { > > super(endpointClass); > > > > registerExtension(HttpComponentVerifierExtension::new); > > } > > The above constructor fails with a no such method error on > > registerExtension. I dropped back to camel 2.19.5 and things work as > > that method is not being used. I would prefer to use the latest > > release 2.21.1 but we have not been able to find a way around the > > problem with registerExtension. Since there does not appear to be any > > documentation around this any information on how to now instantiate > > HttpComponent would be appreciated. > > > > Bill > > > > ______________________________________________________________________ > > The contents of this message, together with any attachments, are > > intended only for the use of the person(s) to which they are addressed > > and may contain confidential and/or privileged information. Further, > > any medical information herein is confidential and protected by law. > > It is unlawful for unauthorized persons to use, review, copy, > > disclose, or disseminate confidential medical information. If you are > > not the intended recipient, immediately advise the sender and delete > this message and any attachments. > > Any distribution, or copying of this message, or any attachment, is > > prohibited. > > ______________________________________________________________________ > The contents of this message, together with any attachments, are intended > only for the use of the person(s) to which they are addressed and may > contain confidential and/or privileged information. Further, any medical > information herein is confidential and protected by law. It is unlawful for > unauthorized persons to use, review, copy, disclose, or disseminate > confidential medical information. If you are not the intended recipient, > immediately advise the sender and delete this message and any attachments. > Any distribution, or copying of this message, or any attachment, is > prohibited. >
