Return-Path: 
 <users-return-38638-apmail-camel-users-archive=camel.apache.org@camel.apache.org>
X-Original-To: apmail-camel-users-archive@www.apache.org
Delivered-To: apmail-camel-users-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id A5460F005
	for <apmail-camel-users-archive@www.apache.org>;
 Tue, 23 Apr 2013 15:39:03 +0000 (UTC)
Received: (qmail 14031 invoked by uid 500); 23 Apr 2013 15:39:03 -0000
Delivered-To: apmail-camel-users-archive@camel.apache.org
Received: (qmail 13990 invoked by uid 500); 23 Apr 2013 15:39:03 -0000
Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@camel.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@camel.apache.org>
List-Post: <mailto:users@camel.apache.org>
List-Id: <users.camel.apache.org>
Reply-To: users@camel.apache.org
Delivered-To: mailing list users@camel.apache.org
Received: (qmail 13982 invoked by uid 99); 23 Apr 2013 15:39:03 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Apr 2013 15:39:03 +0000
X-ASF-Spam-Status: No, hits=-0.7 required=5.0
	tests=RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of cwolf.algo@gmail.com designates
 209.85.212.52 as permitted sender)
Received: from [209.85.212.52] (HELO mail-vb0-f52.google.com) (209.85.212.52)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Apr 2013 15:38:57 +0000
Received: by mail-vb0-f52.google.com with SMTP id w8so727332vbf.11
        for <users@camel.apache.org>; Tue, 23 Apr 2013 08:38:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:x-received:date:message-id:subject:from:to
         :content-type;
        bh=QgdA68cu7UcIUlNEIKhbcaUICg6+tYJZbQabdBeN6aw=;
        b=Z3CgqJJJaeqe1VKPEhbQ3lfNkXvQ/Scj34J604b9QScdxKIfCjLPYXngLCmmH1gqBb
         BGfQNmK8DnILA/HIclQScwvVYIuKucvP4HHI9Vyhji0Z7zYtX6dAwp2vnSOKRfJjvqYu
         azrCQsSIYB/bJzg8R99UNHCJxSGZbUVGEAJyuk0pn+yhrGNPRWX5mcIxtcNv2MCRICq4
         uVaz8n3uzrLGjIKqSgFagqdmK2BUWoB/DWyt62DaYpZv/EdLgPyt/AaOyDEZ5iQFOZfL
         OHZWhkYVIFyAd6s2hIdL715fqhQkmFEmj9LJFUJcTDB2ZLMCfrhlHtSA5YK1eEosGXLU
         zBbw==
MIME-Version: 1.0
X-Received: by 10.220.68.202 with SMTP id w10mr13921213vci.5.1366731516792;
 Tue, 23 Apr 2013 08:38:36 -0700 (PDT)
Received: by 10.59.13.134 with HTTP; Tue, 23 Apr 2013 08:38:36 -0700 (PDT)
Date: Tue, 23 Apr 2013 11:38:36 -0400
Message-ID: 
 <CAK=acOKUmhiUHqm6HF+9MLn-NT_u7wQwdp1_WjzznU6b-YM4Xw@mail.gmail.com>
Subject: Getting a JMS RA-managed ConnectionFactory on JBoss-6.1.0
From: Chris Wolf <cwolf.algo@gmail.com>
To: users@camel.apache.org
Content-Type: text/plain; charset=ISO-8859-1
X-Virus-Checked: Checked by ClamAV on apache.org

I am using the jms:// component in a Spring DSL route in JBoss6.  I
want to publish and subscribe to a topic.  If I package my Camel in a
web app, it cannot do a JNDI lookup on "java:JmsXA", which is the JMS
connection factory managed by a resource adapter.  If I package the
same code as just a plain Spring app and deploy via JBoss "snowdrop"
(kind of like CDI, but with Spring) - then the code successfully looks
up "java:JmsXA".  Does anyone have any experience with accessing JMS
on a JEE server?

I also posted a more detailed JBoss-specific question in this regard at:
https://community.jboss.org/message/809836#809836

Thanks,

Chris