Hi Micky, > Why when you were able to use a browser to access the route, password > exception wasn't thrown ?
are you using the latest trunk? can you verify that the changes identified @ http://fisheye6.cenqua.com/browse/activemq/camel/trunk/components/camel-jetty/src/main/java/org/apache/camel/component/jetty/JettyHttpComponent.java?r1=614080&r2=641800 are in your checkout. With these you should be able to configure a password for the endpoint via a system property or on the command line when prompted. > Have you run this jetty test with https protocol ? yes :-( Early next week I will work on submitting the test case with a key store etc. On 28/03/2008, Micky Santomax <[EMAIL PROTECTED]> wrote: > > > Gary Tully wrote: > > > > I was able to use a browser to access the following route: > > > > Processor proc = new Processor() { > > public void process(Exchange exchange) throws > > Exception { > > > exchange.getOut(true).setBody("Hello World"); > > > } > > }; > > from("jetty:https://localhost:8080/hello").process(proc); > > > > > Sorry Gary, I have run the HttpRouteTest with https protocol but the error > is the same : > > [junit] ------------- Standard Error ----------------- > [junit] 2008-03-28 16:21:32.264::INFO: Logging to STDERR via > org.mortbay.log.StdErrLog > [junit] 2008-03-28 16:21:32.264::INFO: jetty-6.1.8 > [junit] 2008-03-28 16:21:32.571::INFO: Started > [EMAIL PROTECTED]:55631 > [junit] 2008-03-28 16:21:32.657::WARN: EXCEPTION > [junit] java.security.UnrecoverableKeyException: Password must not be > null > ... > > Why when you were able to use a browser to access the route, password > exception wasn't thrown ? > Have you run this jetty test with https protocol ? > > -- > View this message in context: > http://www.nabble.com/Password-error-for-https-endpoint-connection-tp16128569s22882p16354776.html > > Sent from the Camel - Users mailing list archive at Nabble.com. > >
