Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 86761 invoked from network); 16 Oct 2008 01:52:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 16 Oct 2008 01:52:03 -0000 Received: (qmail 65231 invoked by uid 500); 16 Oct 2008 01:51:57 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 65223 invoked by uid 500); 16 Oct 2008 01:51:57 -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: List-Id: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 65212 invoked by uid 99); 16 Oct 2008 01:51:57 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Oct 2008 18:51:57 -0700 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.68.5.9] (HELO relay00.pair.com) (209.68.5.9) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 16 Oct 2008 01:50:49 +0000 Received: (qmail 63132 invoked from network); 16 Oct 2008 01:50:25 -0000 Received: from 124.43.202.32 (HELO ?10.0.0.5?) (124.43.202.32) by relay00.pair.com with SMTP; 16 Oct 2008 01:50:25 -0000 X-pair-Authenticated: 124.43.202.32 Message-ID: <48F69DE0.1090704@wso2.com> Date: Thu, 16 Oct 2008 07:20:24 +0530 From: "Asankha C. Perera" User-Agent: Thunderbird 2.0.0.16 (X11/20080724) MIME-Version: 1.0 To: axis-user@ws.apache.org Subject: Re: AXIS JAVA Client - JMS Transport Authenication References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Sam What is the version of Axis2 and the JMS transport which you are using? i.e. is it the SNAPSHOT versions or a previous release? The JMS transport implementation used by Apache Synapse ESB now lives in the WSCommons project so that Axis2 users can share is more naturally. That has support to define connection properties for outgoing JMS on your axis2.xml for the JMS sender. You could define JNDI properties (i.e. credentials) there for them to be picked up. Anyway, some more background information would help us help you better asankha Kuhn, Samuel M wrote: > I need to provide a username and password to my AXIS client which is > attempting to invoke a web service provider over a TIBCO EMS (JMS > implementation) endpoint. I tried setting the username and password > using the Call.setUsername() and Call.setPassword() methods with no > luck. I also tried adding java.naming.security.principal and > java.naming.security.credentials to the URL with no luck. > > Here's what my String url looks like: > > static String sampleJmsUrl = "jms:/queue.sample?" + > "vendor=JNDI" + > > "&java.naming.factory.initial=com.tibco.tibjms.naming.TibjmsInitialConte > xtFactory" + > > "&java.naming.provider.url=tcp://localhost:7222" + > "&java.naming.security.principal=abc" + > "&java.naming.security.credentials=xyz" > + > > "&ConnectionFactoryJNDIName=QueueConnectionFactory" + > "&deliveryMode=persistent" + > "&priority=5" + > "&ttl=10000" + > "&debug=true"; > > It appears my AXIS client is trying to log on using an "anonymous" user > based on the error message I'm getting from the EMS server. Any help in > resolving this would be appreciated. > > Sincerely, > Sam Kuhn > > --------------------------------------------------------------------- > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org > For additional commands, e-mail: axis-user-help@ws.apache.org > > > --------------------------------------------------------------------- To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org For additional commands, e-mail: axis-user-help@ws.apache.org