ws-soap-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Donny Rose" <>
Subject RE: Problem with xmlns:xsi in SOAP-ENV
Date Sun, 27 Jan 2002 17:05:35 GMT


Without the xsi:schemaLocation it works just fine. But in anycase, that's
not my problem. The question is why Apache SOAP 2.3.1 puts the name/value
pair of xmlns:xsi="" into the
SOAP-ENV, when the value of Constants.NS_URI_CURRENT_SCHEMA_XSI  is . And second, why the method call
Call.buildEnvelope().declareNamespace() has no effect whatsoever.

Any ideas?


  -----Original Message-----
  From: Martin Gainty []
  Sent: Wednesday, June 26, 2002 6:24 PM
  Subject: Re: Problem with xmlns:xsi in SOAP-ENV


  I *thought* you had to specify the xmlns and the xsi:schemaLocation ????
  Here is an example of the use of xlmns and schemaLocation...
  > <?xml version="1.0"?>
  > <BookCatalogue xmlns:xsi=""
  >               xsi:schemaLocation=
  >                "
  >         ...
  > </BookCatalogue>


  Here is another:
  <El1 ID="myID" Description="some text"
     <Recipient>J. Slein</Recipient>
     &l t;Street>309 West Ave.</Street>


  Does this help???
  Anyone else???

  Martin Gainty


  Disclaimer and confidentiality note

  Everything in this e-mail and any attachments relating to the official
business of Laconia Data Systems (LDS) is proprietary to the company. It is
confidential, legally privileged and protected by law. LDS does not own and
endorse any other content. Views and opinions are those of the sender unless
clearly stated as being that of LDS.

  The person addressed in the e-mail is the sole authorised recipient.
Please notify the sender immediately if it has unintentionally reached you
and do not read, disclose or use the content in any way.

  LDS can not assure that the integrity of this communication has been
maintained nor that it is free of errors, virus, interception or


  >From: "Donny Rose"
  >Subject: Problem with xmlns:xsi in SOAP-ENV
  >Date: Sat, 26 Jan 2002 15:27:02 -0500
  >MIME-Version: 1.0
  >Received: from [] by (3.2) with ESMTP id
MHotMailBEE35F4900C84136E852D1426C05046D0; Wed, 26 Jun 2002 12:21:45 -0700
  >Received: (qmail 35553 invoked by uid 500); 26 Jun 2002 19:21:22 -0000
  >Received: (qmail 35544 invoked from network); 26 Jun 2002 19:21:22 -0000
  >Received: from ( by with
SMTP; 26 Jun 2002 19:21:22 -0000
  >Received: from (
[])by [Concentric SMTP Routing 1.0] id
g5QJLQE21290 for ; Wed, 26 Jun 2002 15:21:26 -0400 (EDT)
  >Received: from pf12 (
[])by (8.9.1a)id PAA23432; Wed, 26 Jun
2002 15:21:26 -0400 (EDT)
  >From soap-user-return-14085-mgainty Wed, 26 Jun 2002 12:23:36 -0700
  >Mailing-List: contact; run by ezmlm
  >Precedence: bulk
  >Delivered-To: mailing list
  >X-Priority: 3 (Normal)
  >X-MSMail-Priority: Normal
  >X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
  >Importance: Normal
  >X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
  >X-Spam-Rating: 1.6.2 0/1000/N
  >I am using Apache SOAP 2.3.1, and I can't change the SOAP-ENV's xmlns:xsi
  >value. The request that is sent by Apache SOAP looks likes this:
  >But, the SOAP server that receives this request needs:
  >My understanding is that by default Apache SOAP 2.3.1 is supposed to use
  >newer namespace. In fact, the following debug line before Call.invoke()
  >returns the correct value:
  >debug line: System.err.println( Constants.NS_URI_CURRENT_SCHEMA_XSI );
  >I've tried using Call.buildEnvelope().declareNamespace() method to
  >explicitly declare the correct namespace, but it has no effect
  >I've even tried to declare bogus namespaces, but that has no effect
  >no effect:

  >Am I not using Call.buildEnvelope().declareNamespace() correctly? In any
  >case, how can I tell Apache SOAP 2.3.1 to use the newer xmlns:xsi?
  >I'm greatly perplexed. Please help.
  >Donny Rose
  >Pro-Found Software, Inc.
  >(201) 928-0400
  >(201) 928-1122 (fax)
  >To unsubscribe, e-mail:
  >For additional commands, e-mail:

  Get your FREE download of MSN Explorer at

View raw message