Return-Path: 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 4F766DEBA for ; Fri, 24 May 2013 14:34:43 +0000 (UTC) Received: (qmail 40731 invoked by uid 500); 24 May 2013 14:34:40 -0000 Delivered-To: apmail-cxf-issues-archive@cxf.apache.org Received: (qmail 40299 invoked by uid 500); 24 May 2013 14:34:38 -0000 Mailing-List: contact issues-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 issues@cxf.apache.org Received: (qmail 39877 invoked by uid 99); 24 May 2013 14:34:36 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 May 2013 14:34:36 +0000 Date: Fri, 24 May 2013 14:34:36 +0000 (UTC) From: "Christian Schneider (JIRA)" To: issues@cxf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Closed] (DOSGI-60) Singlebundle Distribution Not working on DmServer 2.0.0 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/DOSGI-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider closed DOSGI-60. ------------------------------------ > Singlebundle Distribution Not working on DmServer 2.0.0 > ------------------------------------------------------- > > Key: DOSGI-60 > URL: https://issues.apache.org/jira/browse/DOSGI-60 > Project: CXF Distributed OSGi > Issue Type: Bug > Affects Versions: 1.2 > Reporter: Matt Inger > > The singlebundle distribution does not seem to be working at all on Spring dmServer 2.0.0. Given my troubles with the jax-ws frontend, which I still can't get working with the singlebundle distribution as documented in DOSGI-55, I figured i'd give the 1.2-SNAPSHOT version a try, hoping it might solve the issue. It seems that with or without the jax-ws frontend, I can't get any web service exposed. > The bundles seem to deploy properly according to the container, however, I cannot access the service, nor do I see the TCP port being listened on (via netstat). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira