Hi
'Injectable' is a custom interface used by the test and its only purpose is to ensure a JAXRS context instance (SecurityContext in
this case) is injected properly, given that the actual resource class (SecureBookStore) is proxified by Spring. For cases like this
one, having a custom utility interface like Injectable IMHO is better than adding methods like setSecurityContext on the application
interfaces like SecureBookInterface.
cheers, Sergey
Andreas Veithen-2 wrote:
Yes, provided that the client propagates the HTTP session, i.e. the
requests to the JAX-RS services contain a JSESSIONID cookie, and that
the Spring Security filters are applied to the JAX-RS endpoints as
well.
Andreas
I am trying to bring my implementation in line with the great examples you
have steered me towards. At the risk of seeming naive, can I ask what the
'Injectable' interface that is implemented in SecureBookStore all about?
How do I implement this?
i.e.
@Path("/bookstorestorage/")
public class SecureBookStore implements SecureBookInterface, Injectable {
...
--
View this message in context:
http://old.nabble.com/Is-it-possible-to-integrate-CXF-JAX-RS-with-Spring-Security-2.0.5---tp27587340p27602675.html
Sent from the cxf-user mailing list archive at Nabble.com.
