Hi, if running your app in OSGi and the Stack-Trace comes from a test using CamelBlueprintTestSupport, this is a know bug. Please provide some more details like camel context XML.
Greetz Andreas 2015-11-18 8:51 GMT+01:00 ehsiung <[email protected]>: > It seems that Camel Restlet component is not resolving sslContextParameters > properties using Camel property placeholder. > > I can see the sslContextParameters took in values from my properties file > and see that my keys are loaded in the ssl debug output. > I however get this error in Restlet: > > Caused by: java.io.FileNotFoundException: > {{bus.ssl.keyManagers.keyStore.resource}} (The system cannot find the file > specified) > at java.io.FileInputStream.open(Native Method) > at java.io.FileInputStream.<init>(FileInputStream.java:138) > at java.io.FileInputStream.<init>(FileInputStream.java:97) > at > > org.restlet.engine.ssl.DefaultSslContextFactory.createSslContext(DefaultSslContextFactory.java:319) > > I'm also curious why Restlet component doesn't take the instantiated > SSLContext and instead copies the properties into Restlet series object for > DefaultSslContextFactory to recreate the SSLContext. > This also causes the issue that classpath resource to the keystore would > work for JsseParameters but fails in Restlet component since Restlet > doesn't > support keystore in classpath. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-Restlet-component-not-using-property-placeholder-resolver-and-not-support-classpath-resource-te-tp5774025.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
