Return-Path: Mailing-List: contact soap-user-help@xml.apache.org; run by ezmlm Delivered-To: mailing list soap-user@xml.apache.org Received: (qmail 25865 invoked from network); 26 Jul 2000 02:32:42 -0000 Received: from e22.nc.us.ibm.com (32.97.136.228) by locus.apache.org with SMTP; 26 Jul 2000 02:32:42 -0000 Received: from southrelay02.raleigh.ibm.com (southrelay02.raleigh.ibm.com [9.37.3.209]) by e22.nc.us.ibm.com (8.9.3/8.9.3) with ESMTP id WAA18960 for ; Tue, 25 Jul 2000 22:10:20 -0500 From: rubys@us.ibm.com Received: from d54mta04.raleigh.ibm.com (d54mta04.raleigh.ibm.com [9.67.228.36]) by southrelay02.raleigh.ibm.com (8.8.8m3/NCO v4.92) with SMTP id WAA25820 for ; Tue, 25 Jul 2000 22:32:41 -0400 Received: by d54mta04.raleigh.ibm.com(Lotus SMTP MTA v4.6.5 (863.2 5-20-1999)) id 85256928.000DF7A3 ; Tue, 25 Jul 2000 22:32:33 -0400 X-Lotus-FromDomain: IBMUS To: soap-user@xml.apache.org Message-ID: <85256928.000DF5A3.00@d54mta04.raleigh.ibm.com> Date: Tue, 25 Jul 2000 22:24:22 -0400 Subject: Re: Deploy Nightmare Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N John Hartman wrote: > > Regarding : No variable NS_URI_BML_ENC defined in class > org.apache.soap.Constants > > I ran into the same issue. I decided to take a direct solution by simply > removing all references to NS_URI_BML_ENC out of the original jsp. > > Has anyone else taken this aproach? And is there anyone familiar enough with > might be wrong with removing references to BML encoding? That is the correct approach. In IBM Soap, there was the beginnings of an experimental BML encoding, but when I converted the package over to org.apache, Sanjiva and I decided not to include the BML support. Unfortunately, I didn't do a complete job in removing all traces... - Sam Ruby