Return-Path: 
 <cxf-issues-return-6533-apmail-incubator-cxf-issues-archive=incubator.apache.org@incubator.apache.org>
Delivered-To: apmail-incubator-cxf-issues-archive@locus.apache.org
Received: (qmail 3323 invoked from network); 14 Apr 2008 18:18:08 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 14 Apr 2008 18:18:08 -0000
Received: (qmail 52688 invoked by uid 500); 14 Apr 2008 18:18:09 -0000
Delivered-To: apmail-incubator-cxf-issues-archive@incubator.apache.org
Received: (qmail 52608 invoked by uid 500); 14 Apr 2008 18:18:09 -0000
Mailing-List: contact cxf-issues-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:cxf-issues-help@incubator.apache.org>
List-Unsubscribe: <mailto:cxf-issues-unsubscribe@incubator.apache.org>
List-Post: <mailto:cxf-issues@incubator.apache.org>
List-Id: <cxf-issues.incubator.apache.org>
Reply-To: cxf-dev@incubator.apache.org
Delivered-To: mailing list cxf-issues@incubator.apache.org
Received: (qmail 52599 invoked by uid 99); 14 Apr 2008 18:18:09 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Apr 2008 11:18:09 -0700
X-ASF-Spam-Status: No, hits=-2000.0 required=10.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Apr 2008 18:17:25 +0000
Received: from brutus (localhost [127.0.0.1])
	by brutus.apache.org (Postfix) with ESMTP id 722FC234C0CF
	for <cxf-issues@incubator.apache.org>; Mon, 14 Apr 2008 11:15:05 -0700 (PDT)
Message-ID: <1744338137.1208196905466.JavaMail.jira@brutus>
Date: Mon, 14 Apr 2008 11:15:05 -0700 (PDT)
From: "Steve Ardis (JIRA)" <jira@apache.org>
To: cxf-issues@incubator.apache.org
Subject: [jira] Commented: (CXF-1494) Issue Using JAX-RS / REST When AOP
 Proxy In Place
In-Reply-To: <1374649414.1206732024323.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org


    [ https://issues.apache.org/jira/browse/CXF-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12588670#action_12588670 ] 

Steve Ardis commented on CXF-1494:
----------------------------------

Sergey / Dan - 

Can you confirm whether or not the fix / patch would have been included in the "cxf-rt-frontend-jaxrs-2.1-incubator-20080411.173632-38.jar" SNAPSHOT release?  If it is included, my initial test failed, but I could still be running with a older version.  Hoping you'll say that it was not.

I am unable to build this myself, as I am receive the following errors from within Eclipse when trying to update the code:

RA layer request failed
svn: REPORT request failed on 'http://svn.apache.org/repos/asf/incubator/cxf/trunk/rt/frontend/jaxrs'
svn: REPORT of 'http://svn.apache.org/repos/asf/incubator/cxf/trunk/rt/frontend/jaxrs': 400 Bad Request (http://svn.apache.org)

I am looking into what this Subversion/Eclipse error means.

> Issue Using JAX-RS / REST When AOP Proxy In Place
> -------------------------------------------------
>
>                 Key: CXF-1494
>                 URL: https://issues.apache.org/jira/browse/CXF-1494
>             Project: CXF
>          Issue Type: Bug
>          Components: REST
>    Affects Versions: 2.1
>            Reporter: Steve Ardis
>            Assignee: Sergey Beryozkin
>             Fix For: 2.1
>
>         Attachments: beans.xml, cxf-1494-2.patch, cxf-1494.patch, Test.java
>
>
> If your beans.xml contains the following entry:
> <jaxrs:server id="services" address="/">
>     <jaxrs:serviceBeans>
>         <ref bean="test" />
>     </jaxrs:serviceBeans>
> </jaxrs:server>
> <bean id="test" class="test.rest.Test" />
> And you have a Spring AOP pointcut defined as:
> <aop:config>
>     <aop:pointcut id="testOperations" expression="execution(* test.rest.*.*(..))" />
>     <aop:advisor advice-ref="transactionAdvice" pointcut-ref="testOperations" />
> </aop:config>
> 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:
> http://incubator.apache.org/cxf/faq.html#FAQ-WhenusingSpringAOPtoenablethingsliketransactionsandsecurity%252CthegeneratedWSDLisverymessedupwithwrongnamespaces%252Cpartnames%252Cetc...
> However, the solution provided in the link does not work due to differences in the APIs between JAX-WS and JAX-RS.
> 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="/">
>     <jaxrs:serviceBeans>
>         <ref bean="test1" />
>         <ref bean="test2" />
>         <ref bean="test3" />
>     </jaxrs:serviceBeans>
> </jaxrs:server>
> 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.