[ 
https://issues.apache.org/activemq/browse/CAMEL-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51592#action_51592
 ] 

Claus Ibsen commented on CAMEL-1570:
------------------------------------

Applied patch to 2.0: 772891

>> See method setReferenceProperties in DefaultComponent in Camel 2.0.
> I'm going to need your help on this one I think.

I had a look at this and the problem is that its a List we want to set of a 
given type, and that we loose the generic type in the list: List<Handler> so we 
dont know the type of the list what it was supposed to contain. 

So I did it manually in the component.

Maybe later we can use a convention that the type should be the setXXX name and 
add list support for URI notations.
But if this is the only component benefit from it, it might not be worth the 
trouble.

> 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
>            Assignee: Claus Ibsen
>         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.

Reply via email to