Return-Path: 
 <issues-return-21285-apmail-cxf-issues-archive=cxf.apache.org@cxf.apache.org>
X-Original-To: apmail-cxf-issues-archive@www.apache.org
Delivered-To: apmail-cxf-issues-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 130D2C50D
	for <apmail-cxf-issues-archive@www.apache.org>;
 Fri, 25 May 2012 17:46:24 +0000 (UTC)
Received: (qmail 73617 invoked by uid 500); 25 May 2012 17:46:24 -0000
Delivered-To: apmail-cxf-issues-archive@cxf.apache.org
Received: (qmail 73581 invoked by uid 500); 25 May 2012 17:46:23 -0000
Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@cxf.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@cxf.apache.org>
List-Post: <mailto:issues@cxf.apache.org>
List-Id: <issues.cxf.apache.org>
Reply-To: dev@cxf.apache.org
Delivered-To: mailing list issues@cxf.apache.org
Received: (qmail 73573 invoked by uid 99); 25 May 2012 17:46:23 -0000
Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 May 2012 17:46:23 +0000
Received: from isssues-vm.apache.org (localhost [127.0.0.1])
	by issues-vm (Postfix) with ESMTP id 9C293142831
	for <issues@cxf.apache.org>; Fri, 25 May 2012 17:46:23 +0000 (UTC)
Date: Fri, 25 May 2012 17:46:23 +0000 (UTC)
From: "Daniel Kulp (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: <798938244.3130.1337967983642.JavaMail.jiratomcat@issues-vm>
In-Reply-To: 
 <487151193.68627.1327356340927.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (CXF-4058) If CXF is last in Karaf feature list,
 endpoints aren't bound
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


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

Daniel Kulp updated CXF-4058:
-----------------------------

    Fix Version/s: NeedMoreInfo


Any chance you could re-try with CXF 2.6?   There have been a ton of OSGi enhancements since 2.5.0 and this may likely already be fixed.   Specifically, some work around the HTTP transport and how that is wired into pax-web may have resolved this already.
                
> If CXF is last in Karaf feature list, endpoints aren't bound
> ------------------------------------------------------------
>
>                 Key: CXF-4058
>                 URL: https://issues.apache.org/jira/browse/CXF-4058
>             Project: CXF
>          Issue Type: Bug
>          Components: OSGi
>    Affects Versions: 2.5
>         Environment: Talend Service Factory 2.5.0.0 (Karaf 2.2.4, CXF 2.5.0)
>            Reporter: Chris Dolan
>            Priority: Minor
>             Fix For: NeedMoreInfo
>
>
> [I apologize in advance that this bug report has a lot of guesswork in it. I've found a workaround so I've marked this as "Minor", but it took me a week to find my workaround and I can't figure where the root cause is.]
> If I write my "featuresBoot" property in org.apache.karaf.features.cfg like this, everything works:
>   featuresBoot=config,ssh,management,activemq-spring,cxf,webconsole,my-custom-feature
> But if I (accidentally) move my feature to the front of the list like so:
>   featuresBoot=my-custom-feature,config,ssh,management,activemq-spring,cxf,webconsole
> then I get 404's for the resources and "No services have been found." on the CXF services list.
> My custom feature contains a JAX-RS application which is bootstrapped with a META-INF/spring/beans.xml file containing beans roughly like this:
>     <jaxrs:server id="admin" address="/path/to/my/application">
>         <jaxrs:inInterceptors>
>             <ref bean="traceInboundStart"/>
>         </jaxrs:inInterceptors>
>         <jaxrs:outInterceptors>
>             <ref bean="traceOutboundDone"/>
>         </jaxrs:outInterceptors>
>         <jaxrs:serviceBeans >
>             <ref bean="mySvc"/>
>         </jaxrs:serviceBeans>
>         <jaxrs:providers>
>             <ref bean="jaxRsAuthFilter"/>
>         </jaxrs:providers>
>     </jaxrs:server>
> Reloading the bundles in "my-custom-feature" fixes the problem (the WADL links appear on the services list and the endpoint URLs respond correctly). In both scenarios ("my-custom-feature" at the front or back of the featuresBoot list), the log messages seem to be nearly identical.
> A really confusing part is that in *both* cases, I see this log message which seems to suggest success:
> [INFO] Setting the server's publish address to be /path/to/my/application
> logger = org.apache.cxf.endpoint.ServerImpl
> thread = SpringOsgiExtenderThread-2
> So, clearly CXF is getting the JAX-RS application successfully, but somehow that's not being mapped all the way through to the OSGi HTTP service.
> The only other logs that appear relevant appear to be these:
> [INFO] SPI-Provider Manifest header found in bundle: org.apache.cxf.bundle
> [INFO] Binding bundle: [org.apache.cxf.bundle_2.5.0 [191]] to http service
> Those happen just before the "Setting the server's publish address..." message but after the Spring "Found mandatory OSGi service for bean..." resolution messages in the failing scenario.
> I request either 1) a fix so the CXF feature is order independent or 2) a troubleshooting log message to indicate that the resources are bound too late to help others diagnose this problem more quickly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira