Return-Path: 
 <dev-return-20532-apmail-camel-dev-archive=camel.apache.org@camel.apache.org>
Delivered-To: apmail-camel-dev-archive@www.apache.org
Received: (qmail 50905 invoked from network); 26 Jul 2010 15:49:17 -0000
Received: from unknown (HELO mail.apache.org) (140.211.11.3)
  by 140.211.11.9 with SMTP; 26 Jul 2010 15:49:17 -0000
Received: (qmail 97618 invoked by uid 500); 26 Jul 2010 15:49:17 -0000
Delivered-To: apmail-camel-dev-archive@camel.apache.org
Received: (qmail 97576 invoked by uid 500); 26 Jul 2010 15:49:16 -0000
Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@camel.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@camel.apache.org>
List-Post: <mailto:dev@camel.apache.org>
List-Id: <dev.camel.apache.org>
Reply-To: dev@camel.apache.org
Delivered-To: mailing list dev@camel.apache.org
Received: (qmail 97568 invoked by uid 500); 26 Jul 2010 15:49:16 -0000
Delivered-To: apmail-activemq-camel-dev@activemq.apache.org
Received: (qmail 97565 invoked by uid 99); 26 Jul 2010 15:49:16 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Jul 2010 15:49:16 +0000
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.22] (HELO thor.apache.org) (140.211.11.22)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Jul 2010 15:49:14 +0000
Received: from thor (localhost [127.0.0.1])
	by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o6QFmp8I019911
	for <camel-dev@activemq.apache.org>; Mon, 26 Jul 2010 15:48:52 GMT
Message-ID: <2871652.52561280159331840.JavaMail.jira@thor>
Date: Mon, 26 Jul 2010 11:48:51 -0400 (EDT)
From: "William Tam (JIRA)" <jira@apache.org>
To: camel-dev@activemq.apache.org
Subject: [jira] Updated: (CAMEL-2991) Restart CamelContext won't restart
 services on CxfBeanEndpoint
In-Reply-To: <15847924.51041280027031829.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: ae95407df07c98740808b2ef9da0087c
X-Virus-Checked: Checked by ClamAV on apache.org


     [ https://issues.apache.org/activemq/browse/CAMEL-2991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

William Tam updated CAMEL-2991:
-------------------------------

    Attachment:     (was: CAMEL-2991.patch)

> Restart CamelContext won't restart services on CxfBeanEndpoint
> --------------------------------------------------------------
>
>                 Key: CAMEL-2991
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2991
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-core, camel-cxf
>            Reporter: William Tam
>            Assignee: William Tam
>             Fix For: 2.5.0
>
>         Attachments: CAMEL-2991-test-case.txt
>
>
> A route that sends to a CxfBean destination is unusable after the CamelContext has been stopped and re-started.  The following is an example of a route that demonstrates the problem.
> {code}
> 	<camelContext id="camel" xmlns="http://camel.apache.org/schema/spring">
> 		<route>
> 			<from uri="jetty:http://localhost:9000?matchOnUriPrefix=true" />
> 			<to uri="cxfbean:customerServiceBean" />
> 		</route>
> 	</camelContext>
> 	<util:list id="customerServiceBean">
> 		<bean class="org.apache.camel.component.cxf.jaxrs.testbean.CustomerService" />
> 	</util:list>
> {code}
> The follow issues have been identified.
> 1) SendProcessor should implement the Navigate interface so that its children (if they are Services) can be managed by the lifecycle methods.  This will address any destination endpoint that requires services to be re-started.
> 2) CxfBeanEndpoint should be a Service itself.  The reason why the start() on CxfBeanEndpoint gets called during the first start is because CxfBeanComponent.start() gets invoked during route definition initialization.   The problem is that re-starting doesn't trigger the CxfBeanComponent.start() method.  Therefore, putting the hook in CxfBeanComponent to start/stop CxfBeanEndpoint was a bug.
> 3) The default type converter which is a Service won't get "re-started' as the (lazy-instantiation) getTypeConverter() method won't perform addService() on a created but "stopped' typeConverter.  We need to discuss the correct remedy since I am not sure how to fix it.  It is kind of strange that the type converter is a service (which has the start/stop semantics) and yet it can be used even the CamelContext is stopped (or never started).  In the patch, I just set the type converter to null in DefaultCamelContext doStop() for now.

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