Return-Path: <m.hansen23@verizon.net>
Mailing-List: contact axis-user-help@xml.apache.org; run by ezmlm
Delivered-To: mailing list axis-user@xml.apache.org
Received: (qmail 1320 invoked from network); 22 Apr 2002 20:12:32 -0000
Received: from out006pub.verizon.net (HELO out006.verizon.net)
 (206.46.170.106)
  by daedalus.apache.org with SMTP; 22 Apr 2002 20:12:32 -0000
Received: from mhansenlaptop ([129.44.48.136]) by out006.verizon.net
          (InterMail vM.5.01.04.05 201-253-122-122-105-20011231) with SMTP
          id <20020422201102.UHPL27046.out006.verizon.net@mhansenlaptop>
          for <axis-user@xml.apache.org>; Mon, 22 Apr 2002 15:11:02 -0500
Reply-To: <m.hansen23@verizon.net>
From: "Mark Hansen" <m.hansen23@verizon.net>
To: <axis-user@xml.apache.org>
Subject: JMS as transport
Date: Mon, 22 Apr 2002 16:11:57 -0400
Message-ID: <MKEOJHBMOKGDJKBMMKBFCEOECPAA.m.hansen23@verizon.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Can anyone tell me if AXIS provides a simply way of using JMS as the SOAP
transport layer instead of HTTP?  If not, are there any plans for this?

Thanks,

Mark Hansen