Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 71426 invoked from network); 7 Aug 2007 15:57:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 7 Aug 2007 15:57:22 -0000 Received: (qmail 5054 invoked by uid 500); 7 Aug 2007 15:57:02 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 5032 invoked by uid 500); 7 Aug 2007 15:57:02 -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 5013 invoked by uid 99); 7 Aug 2007 15:57:02 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Aug 2007 08:57:02 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [69.3.207.123] (HELO mailman.larich.com) (69.3.207.123) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Aug 2007 15:56:39 +0000 Received: from mail.larich.com (localhost [127.0.0.1]) by mailman.larich.com (8.13.1/8.13.1) with ESMTP id l77FtFEf022927 for ; Tue, 7 Aug 2007 11:55:15 -0400 From: "Hillel Seltzer" To: axis-user@ws.apache.org Subject: RE: Axis and wss4j debugging Date: Tue, 7 Aug 2007 11:55:15 -0400 Message-Id: <20070807154601.M78910@larich.com> In-Reply-To: <8B0552BD5078074B87F6DC3A7EAB76EB0195F804@MSGMROCLS2WIN.DMN1.FMR.COM> References: <8B0552BD5078074B87F6DC3A7EAB76EB0195F804@MSGMROCLS2WIN.DMN1.FMR.COM> X-Mailer: Open WebMail 2.51 20050228 X-OriginatingIP: 172.17.200.114 (hss) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org No, the handler is for sure on my class path, and it is found when I put it in the wsdd. The problem is that the wsdd is somehow messing up the transport. Let's forget about the wss4j handler and just worry about getting the client to connect using a wsdd so that it should get a "missing security token" SOAP error. Consider the following wsdd file: Without any wsdd file, I get a "missing security token" error. That should happen. With the above wsdd file, the debug log shows that the program builds the outgoing XML message, then just does not establish a connection to send it. Here is the end of the debug log: - 441391.02005-01-01T05:00:00.000Ztrue - Enter: AxisClient::invoke - Enter: AxisClient::invoke - EngineHandler: null - EngineHandler: null - Enter: SimpleChain::invoke - Enter: SimpleChain::invoke - Exit: SimpleChain::invoke - Exit: SimpleChain::invoke - org.apache.axis.i18n.resource::handleGetObject(semanticCheck00) - org.apache.axis.i18n.resource::handleGetObject(semanticCheck00) - Doing SOAP semantic checks... - Doing SOAP semantic checks... - Exit: AxisClient::invoke - Exit: AxisClient::invoke - Exit: Call::invoke() - Exit: Call::invoke() - Exit: Call::invoke(ns, meth, args) - Exit: Call::invoke(ns, meth, args) - axis.Call.invoke: 178 GetOHSalesTaxByZipCode - axis.Call.invoke: 178 GetOHSalesTaxByZipCode Exception in thread "main" java.lang.NullPointerException at larich.getohtax.GetOHTax.main(GetOHTax.java:39) Thanks. ---Hillel On Tue, 7 Aug 2007 09:56:08 -0400, Walker, Jeff wrote > Hillel, > I'm not really not sure, but it most likely is a classpath issue. I > don't think it can find the class. > See this below for a very similar problem like yours ?? > http://mail-archives.apache.org/mod_mbox/ws-axis-user/200412.mbox/%3COFE > D4E8C07.DB96DB7C-ON85256F70.006A3914-85256F70.006AFEA8@pheaa.org%3E > Regards, > -jeff > --------------------------------------------------------------------- To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org For additional commands, e-mail: axis-user-help@ws.apache.org