[
https://issues.apache.org/activemq/browse/CAMEL-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Hunt updated CAMEL-1570:
------------------------------------
Attachment: jetty-handlers-test.txt
jetty-handlers.txt
1.x changes.
I have deleted the previous patches given that there was an error. Previously I
attached the handlers to the first context that the server could provide (as is
done for the session - is that a bug also?). What is now done is that the
handlers are attached to the context created at the time the servlet is created.
I have included a new unit test to test out the handler functionality. I use a
Jetty supplied statistics handler to ensure that it counts my requests coming
through. Naturally if the handler was not added to the context then no requests
would be counted.
In addition the unit test exercises multiple handlers being included for a
different context. This tests that multiple handlers are catered for and that
one context's handlers are not invoked for another's.
I have also tidied up the test cases so that they are able to:
(i) execute on a file system that has spaces in the path name; and
(ii) execute on a system that is not running postgres.
On the latter I noticed that port 5432 was being used for some of the tests.
This port is used by postgres. Given that I had postgres running on my machine
the tests could not complete. All tests now use a port number around 9080.
> Jetty component is unable to be configured for security
> -------------------------------------------------------
>
> Key: CAMEL-1570
> URL: https://issues.apache.org/activemq/browse/CAMEL-1570
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-jetty
> Affects Versions: 1.6.0, 2.0-M1
> Environment: NA
> Reporter: Christopher Hunt
> Attachments: jetty-handlers-test.txt, jetty-handlers.txt
>
>
> The Jetty component is presently unable to be configured for security. A
> general purpose mechanism so that the Jetty component can be configured would
> be useful. The following URI based option is proposed:
> ||Name||Default Value||Description||
> |handlers|null| Specifies a comma delimited set of instances in your Registry
> (such as your Spring ApplicationContext). These instances are added to the
> Jetty servlet context|
> Here is an example URI:
> {code}
> jetty:http://0.0.0.0:9080/MyService?handlers=securityHandler
> {code}
> This could refer to something like the following Spring configuration:
> {code}
> <!-- Jetty Security handling -->
> <bean id="userRealm" class="org.mortbay.jetty.plus.jaas.JAASUserRealm">
> <property name="name" value="tracker-users" />
> <property name="loginModuleName" value="ldaploginmodule" />
> </bean>
> <bean id="constraint" class="org.mortbay.jetty.security.Constraint">
> <property name="name" value="BASIC" />
> <property name="roles" value="tracker-users" />
> <property name="authenticate" value="true" />
> </bean>
> <bean id="constraintMapping"
> class="org.mortbay.jetty.security.ConstraintMapping">
> <property name="constraint" ref="constraint" />
> <property name="pathSpec" value="/*" />
> </bean>
> <bean id="securityHandler"
> class="org.mortbay.jetty.security.SecurityHandler">
> <property name="userRealm" ref="userRealm" />
> <property name="constraintMappings" ref="constraintMapping" />
> </bean>
> {code}
> I have attached proposed changes to the 1.6 branch. I imagine that 2.0 should
> be quite similar.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
