Sergey Beryozkin-3 wrote:
> 
> 
>> 
>> If you don't add the <aop:scoped-proxy> and <aop:aspectj-autoproxy> tags,
>> you'll encounter an error:  "object is not an instance of declaring
>> class."
>> 
>> The only problem I'm noticing right now is that method overloading
>> doesn't
>> work when using Spring's AOP stuff.  That's not a big deal, though, and
>> right now I'm just ecstatic that spring-security is working.
> 
> Is it on a JAXRS or JAXWS invocation path ? Can you post a sample java
> code please for "myServiceBean" ?
> 

It's on a JAXRS invocation path.

------- MyService.java -------
@Path( "/myService/" )
@ProduceMime( "application/xml" )
@WebService( name = "MyService" )
public class MyService {

    public MyService() {

    }

    @GET
    @Path( "/tryThis/{id}/{name} )
    @ProduceMime( "application/xml" )
    @Secured( "ROLE_ADMINISTRATOR" )
    public List<OurObject> tryThis( @PathParam( "id" ) String id,
@PathParam( "name" ) String name ) {

        // do stuff.
    }

    @GET
    @Path( "/tryThis/{id} )
    @ProduceMime( "application/xml" )
    @Secured( "ROLE_ADMINISTRATOR" )
    public List<OurObject> tryThis( @PathParam( "id" ) String id ) {

        return tryThis( id, "Fake Name" );
    }
}



> Is 'provisioningBean' different to myServiceBean ?
> 

No, sorry, provisioningBean should be myServiceBean.

I'm hoping to replace my my existing HTTP authentication with WS-Security... 
I'll let you know how that goes.  :)

Thank you,
 - Dave
-- 
View this message in context: 
http://www.nabble.com/Spring-Security-annotations-in-CXF--tp20823712p20846009.html
Sent from the cxf-user mailing list archive at Nabble.com.

Reply via email to