**My previous post got mangled by my email service--Sorry!
Maybe it will be helpful for me to provide a bit more detail. Here is the content of a
web services call that doesn't work:
POST /imapi HTTP/1.0
Content-Type: text/xml; charset=utf-8
Accept: application/soap+xml, application/dime,
My bad - in my previous post I said client-config.xml when I really meant client-config.wsdd. Sorry for the confusion... Tony --- On Thu 07/22, Anthony Piazza < [EMAIL PROTECTED] > wrote:From: Anthony Piazza [mailto: [EMAIL PROTECTED]: [EMAIL PROTECTED]: Thu, 22 Jul 2004 12:30:45 -040
t-config.wsdd is in your classpath.--mAnand Natrajan wrote:>Anthony,>>My bad - I read your email to the opposite effect. Of course, you could>simply set that parameter to true...>>Re: control over Axis jar - this is the _client_-side jar we're talking>about, not the
called . Inside that, add the following XML segment.
Can't guarantee whether it'll work or not, but it may remove the xsi namespace.
Good luck!
Anand
On Tue, 20 Jul 2004, Anthony Piazza wrote:
I am using Axis as a client to a web service that uses WASP. The problem I
I am using Axis as a client to a web service that uses WASP. The problem I am having
is that the service doesn't work with the more recent versions of Axis (1.1). It turns
out that the app server (JBoss) we are using includes the latest version of Axis as
part of it's standard deployment (which
