I couldn't be sure with digging into it further but you have a 1.5.x installed, the semantic versioning indicates that the bundle you require be something greater than 1.4.x, but you get a wiring failure. There's a bug reported against websockets for Camel 2.18 for just the same error and the Maven repo shows a clear change in the bundling/jar artifact at that point. I don't have that javax mail bundle/jar in my local repo but you could look in yours and crack it open and look at the exports int he Manifest and see if it is exporting everything properly. And compare that to 1.4.5 for example.
You could also try Camel 2.17.2 or 2.17.3 to see if it was fixed in one of those but I don' t know that it was. On Tue, Aug 9, 2016 at 10:21 AM, Vince Iglehart < vince.igleh...@kniferiver.com> wrote: > I'm not sure if I understand exactly what your saying. Are you thinking > the > java packaging structure for objects inside javax.mail component may have > changed from Java 1.4 to 1.5? > > > When I look at the dependencies in the features.xml located at > https://repo1.maven.org/maven2/org/apache/camel/karaf/ > apache-camel/2.17.1/apache-camel-2.17.1-features.xml > > It appears that 2.17.1 requires javax.mail 1.5.5. Is that what your > understanding is? > > Could I somehow upgrade the javax.mail feature? Do I need to downgrade to > an older version of Camel? What are my options? > > > > -- > View this message in context: http://camel.465427.n5.nabble. > com/Installing-Camel-SQL-Unable-to-resolve-javax-mail- > tp5786203p5786211.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
