Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Received-SPF: pass (asf.osuosl.org: domain of davanum@gmail.com designates
 64.233.170.195 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=qov4862ci2fwMcqlRx4ojqTHj6CzbGNG7Bp0hLPoZQuzGxMGAVvTSKHyXtm9kiAXige/jEE3ZErXGt4qEY8FKRCTMyoLHRyOerJKG6Sh9VO0QC9rnKLSP+JmZhKQjs4oDqA0i6T7dketfgnqX9aROwJfFh2IRLdK/o4Gz8mkN0M=
Message-ID: <19e0530f050808055037e22c14@mail.gmail.com>
Date: Mon, 8 Aug 2005 08:50:36 -0400
From: Davanum Srinivas <davanum@gmail.com>
Reply-To: dims@apache.org
To: axis-dev@ws.apache.org
Subject: Re: Question for Dims
In-Reply-To: <8ae82b1205080805465accd672@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <8ae82b1205080805465accd672@mail.gmail.com>

Yes, it's ok to use ALLOW_FORM_OPTIMIZATION (It's a ugly hack we need
under some conditions. I hate it, but no way around it currently.)

thanks,
-- dims

On 8/8/05, mtim <mtimour@gmail.com> wrote:
> Hello dims,
>=20
> We  have web service that is running perfectly under Axis 1.1 and
> fails under 1.2 because of the change that was introduced in Axis 1.2
>  I checked CVS and found that  you made a change in
> org.apache.axis.SOAPPart.setCurrentForm(Object, int) method which now
> executes only if ALLOW_FORM_OPTIMIZATION  property is set to true.
>=20
> Our rpc handler  transforms incoming SOAP message to Document and back
> to SOAP and then sets it on message context. So if try to do something
> with that message , after the transformation, then I'm  getting
> ClassCastException from:
> org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:725)
> What  I noticed is that when our handler handles a SOAP request ,
> message context contains ALLOW_FORM_OPTIMIZATION property which is set
> to false. If I set that property to true then everything works fine -
> no exceptions.
>=20
> Can help me to understand what is behind "ALLOW_FORM_OPTIMIZATION" proper=
ty.
> Is it safe for me to set "ALLOW_FORM_OPTIMIZATION" to true in the
> handler ?  Is there another workaround to solve this problem ?
>=20
> I would appreciate any of  your ideas.
>=20
> Thanks ,
>=20
> Timour
>=20


--=20
Davanum Srinivas -http://blogs.cocoondev.org/dims/