cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Ardis (JIRA)" <>
Subject [jira] Created: (CXF-1494) Issue Using JAX-RS / REST When AOP Proxy In Place
Date Fri, 28 Mar 2008 19:20:24 GMT
Issue Using JAX-RS / REST When AOP Proxy In Place

                 Key: CXF-1494
             Project: CXF
          Issue Type: Bug
          Components: REST
    Affects Versions: 2.1
            Reporter: Steve Ardis

If your beans.xml contains the following entry:

<jaxrs:server id="services" address="/">
        <ref bean="test" />

<bean id="test" class="" />

And you have a Spring AOP pointcut defined as:

    <aop:pointcut id="testOperations" expression="execution(**.*(..))" />
    <aop:advisor advice-ref="transactionAdvice" pointcut-ref="testOperations" />

no mapping to the test bean are mapped and method cannot be invoked - it fails with "No operation
found for path: /test/string/"

If you comment out the contents of <aop:config> everything works fine.

This link describes the problem with JAX-WS and the same issue probably applies to JAX-RS:

However, the solution provided in the link does not work due to differences in the APIs between

I have a dumbed-down Maven project that I can zip up and provide if necessary.

Is there a suggested way around this problem for JAX-RS?

Is there a reason that, if the instance of the class that JAX-RS sees is a proxy object, that
it can't get the underlying class information by drilling into the proxy object, thereby eliminating
the necessity to define the serviceClass information (as in the JAX-WS "fix")?  Ideally ,
I'd like to be able to do the following:

<jaxrs:server id="services" address="/">
        <ref bean="test1" />
        <ref bean="test2" />
        <ref bean="test3" />

without having to define separate jaxrs server(s) (as in the JAX-WS "fix").

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message