Return-Path: Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 9952 invoked by uid 500); 11 Aug 2003 17:03:35 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 9941 invoked from network); 11 Aug 2003 17:03:35 -0000 Message-ID: <20030811170339.14693.qmail@web20413.mail.yahoo.com> Date: Mon, 11 Aug 2003 10:03:39 -0700 (PDT) From: srinivas reddy Subject: Help with JMS in AXIS To: axis-user@ws.apache.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi, I been working on this problem for quite some time. I really appreciate if anybody can help me. My questions are 1. When a method of a web service is invoked, it sends a series of JMS message s to client queue and returns an integer. How do I design this with AXIS & JMS?. I coded this as normal JMS application without using JMS transport etc as the response is not a JMS message. But the service is not getting deployed when I include sender.send(...) statement. Why is this so? 2. JNDI context is unable to lookup QueueConnectionFactory from inside the web service. I am running web service on the same machine where J2EE server is running and I used following code Context c = new InitialContext(); c.lookup("QueueConnectionFactory"); If the same application is not ran as web service, it works. Why is this happening? Please point out resources for using JMS with AXIS. I searched google but all I found is how to use JMS transport in AXIS. tia, Srinivas ===== I am not afraid of losing. But I don't like it. __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com