-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 19, 2002 3:14 PM
To: [EMAIL PROTECTED]
Subject: RE: running with axis
Is your code swallowing an exception somewhere, so you can't see it?
Tim Lee <[EMAIL PROTECTED]> 11/19/2002 10:47 AM
Please respond to axis-user
To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
cc:
Subject: RE: running with axis
Yes, I point to all Axis jar files and my jar files containing my code. It
executes the code except the call:invoke() returns a null response. I
checked my server logs and there was no attempt at a connection. I didn't
change anything except I'm running command line.
-----Original Message-----
From: Bahman Kalali [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 19, 2002 1:49 PM
To: [EMAIL PROTECTED]
Subject: Re: running with axis
Did you check your classpath? Do you have all required jar files in your
classpath while using running your app on command line?
--Bahman
----- Original Message -----
From: "Tim Lee" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, November 19, 2002 1:40 PM
Subject: running with axis
> I'm using visual cafe to run a program that connects to a webservice using
> stubs generated by WSDL2Java. I'm trying to figure out some problems I'm
> having running with axis. If I take a test program that runs perfectly
fine
> in cafe and run it from the command line, the response from the
> call.invoke() is returned as null. It's not even connecting to the
server.
> But if I run the same classes from within cafe it works fine. Any idea as
> to why this would be happening?
>
***************************************************************************
> The information contained in this message is intended only for the
> confidential use of the recipient(s) named above. This message is
privileged
> and confidential. If the reader of this message is not the intended
> recipient or any agent responsible for delivering it to the intended
> recipient, you are hereby notified that you have received this document in
> error and that any review, dissemination, distribution, or copying of this
> message is strictly prohibited. If you have received this communication in
> error, please notify us immediately. SMG reserves the right to monitor and
> review all content sent to and from this email address. Messages sent to
and
> from this address may be stored on the SMG email system.
***************************************************************************
The information contained in this message is intended only for the
confidential use of the recipient(s) named above. This message is privileged
and confidential. If the reader of this message is not the intended
recipient or any agent responsible for delivering it to the intended
recipient, you are hereby notified that you have received this document in
error and that any review, dissemination, distribution, or copying of this
message is strictly prohibited. If you have received this communication in
error, please notify us immediately. SMG reserves the right to monitor and
review all content sent to and from this email address. Messages sent to and
from this address may be stored on the SMG email system.
*************************************************************************** The information contained in this message is intended only for the confidential use of the recipient(s) named above. This message is privileged and confidential. If the reader of this message is not the intended recipient or any agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately. SMG reserves the right to monitor and review all content sent to and from this email address. Messages sent to and from this address may be stored on the SMG email system.
