Return-Path: X-Original-To: apmail-cxf-dev-archive@www.apache.org Delivered-To: apmail-cxf-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 19E976A34 for ; Mon, 16 May 2011 09:43:34 +0000 (UTC) Received: (qmail 78610 invoked by uid 500); 16 May 2011 09:43:33 -0000 Delivered-To: apmail-cxf-dev-archive@cxf.apache.org Received: (qmail 78559 invoked by uid 500); 16 May 2011 09:43:33 -0000 Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list dev@cxf.apache.org Received: (qmail 78551 invoked by uid 99); 16 May 2011 09:43:33 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 May 2011 09:43:33 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of sberyozkin@gmail.com designates 209.85.214.41 as permitted sender) Received: from [209.85.214.41] (HELO mail-bw0-f41.google.com) (209.85.214.41) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 May 2011 09:43:29 +0000 Received: by bwz17 with SMTP id 17so4493287bwz.0 for ; Mon, 16 May 2011 02:43:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=LsMy2Z4yO2d6tiuqKylVkMGg+HktsDHN3XHkePJrfCQ=; b=Hkiqt4vv11QpQYCfkdrZL3Ljo6Y7V2TC4rhzAbgWwxHIrcq3WBllJC0EunGVSocHYO MrEcSIDwH5fg0qE9NnnadAYcoi35szw0LSKjsdRyvEhFDqhcURjLyJCkrAka3PaVGFuu nopCCCnHWFmrRSQoLwpkwCcMOB4GBkBg7Ru34= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=Wv1cLEuEuIGI9xoalanGpANJJ3j64XfP5g2BA+HmGKWHtP6GPYpOF/oDxb3BISjt0g 1UGyoqwlNFq2ej/4hkLJLVkFrTKjbzEdqI3+RYLQTa16TR+CDhchZVwhvZNYJAca1mGv aUKr78oGFahJNS9gKIR9M1XIM29p/Lxuisfn8= MIME-Version: 1.0 Received: by 10.204.10.81 with SMTP id o17mr3888741bko.94.1305538986816; Mon, 16 May 2011 02:43:06 -0700 (PDT) Received: by 10.204.179.211 with HTTP; Mon, 16 May 2011 02:43:06 -0700 (PDT) In-Reply-To: References: Date: Mon, 16 May 2011 10:43:06 +0100 Message-ID: Subject: Re: CustomerService Project From: Sergey Beryozkin To: dev@cxf.apache.org Content-Type: text/plain; charset=ISO-8859-1 Hi Ryan I can see you trying very hard but I'm not sure what are trying to do with Customer, ICustomerState, and 10 other methods that you have there. I've only asked you to have Customer returning its state with the help of subresource locator, and I haven't asked it so that I can make this project more difficult for you but rather for you to feel what you can do with JAX-RS, before you move on the the integration part. May be I'm wrong with my strategy, I'm not sure. As I said in the previous email, have Customer state set to some initial values. Have only 2 methods, one is sub-resource locator (this is a JAX-RS resource method which returns the object which will complete the processing of the request and in our case it has to be Customer object, it has to be "this" for this particular case) and the other method is the final resource method with @GET which will return the actual state and again, it has to be 'this' - because Customer is XmlRootElement annotated. Custom ResourceProvider for a 2nd endpoint needs to create Customer on every request. It's irrelevant what this provider does, as far as the task of returning Customer's state is concerned, I'm only asking you to have a custom provider for you to understand how you can have the lifecycle of JAX-RS root resources managed. Lets have thisi task finished asap because what needs to be done is the evaluation of how CXF JAXWS integrates with EJB and then we need to figure out how to follow a similar approach with JAX-RS and then we need to deal with the rest of integration issues, there's a lot of work there so we really need to finish the "catching up with JAX-RS" task asap. Please start checking how CXF JAXWS integrates with EJB. Don't spend time on the EJB tutorial with Glassfish - I'm sure it's all of high quality there, but you need to find the fastest way to the target and thus see how CXF JAX-WS manages it. Try JBoss-CXF integration or Jonas and EasyBeans, I've checked the link Guillaume Sauthier posted earlier on and implementing EJB service factory/resource provider looked simple. Also, please don't send all the details of the log traces to the dev list, please send them to me directly but keep updating the dev list on the progress. Ping me privately or on #cxf as well Thanks, Sergey On Mon, May 16, 2011 at 4:45 AM, Ryan Zoerner wrote: > I mentioned that it works fine when done a certain way, but unfortunately, > it works just fine without the @GET annotated method, without the @GET and > without the method. > > Thanks, > > Ryan > > http://pages.cs.wisc.edu/~zoerner/downloads/dev/samples/customerservice/testing/unfortunately_works_fine_like_this/ > -- Sergey Beryozkin Application Integration Division of Talend http://sberyozkin.blogspot.com