Mailing-List: contact users-help@flex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@flex.apache.org
From: Christofer Dutz <christofer.dutz@c-ware.de>
To: "users@flex.apache.org" <users@flex.apache.org>
Subject: AW: AW: Blaze DS 4.7.1 - bug found
Thread-Topic: AW: Blaze DS 4.7.1 - bug found
Thread-Index: AQHQ4L7fcTqNhDlg0EOy1ZlHIPof8J4g2scg
Date: Fri, 28 Aug 2015 04:59:35 +0000
Message-ID: 
 <DB5PR05MB1285C4B4F75620F91D0715C5A26E0@DB5PR05MB1285.eurprd05.prod.outlook.com>
References: 
 <DUB129-W77960B15C44039E844842CB600@phx.gbl>,<CAOeExM4+wjN1hQu4afgmVk-DaWspwN5q7osbAjDxhHCpEtmguw@mail.gmail.com>,<DUB129-W28490FC0B5B845E9331AB5CB600@phx.gbl>,<CAAGkw=BoX1c7G6Yi7Sr3E0KorLQhWZYb1n344QhQGu2n6Xgf9g@mail.gmail.com>,<DB5PR05MB12852A415E58F84073170366A2600@DB5PR05MB1285.eurprd05.prod.outlook.com>
 <DUB129-W6903300EF1E302A19EB59DCB6F0@phx.gbl>
In-Reply-To: <DUB129-W6903300EF1E302A19EB59DCB6F0@phx.gbl>
Accept-Language: de-DE, en-US
Content-Language: de-DE
received-spf: None (protection.outlook.com: c-ware.de does not designate
 permitted sender hosts)
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Aug 2015 04:59:35.8058
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 9d387546-1437-4b89-846c-691d64a7e74d
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB5PR05MB1286

Hi Miguel,

It took a little for me to dig into your problem, but I think I now know wh=
at you are refereing to.
I'll look into it and probably make a 4.8.0-SNAPSHOT available as soon as p=
ossible.

Chris

-----Urspr=FCngliche Nachricht-----
Von: Miguel Ferreira [mailto:miguel.cd.ferreira@hotmail.com]=20
Gesendet: Donnerstag, 27. August 2015 13:52
An: users@flex.apache.org
Betreff: RE: AW: Blaze DS 4.7.1 - bug found

Hi all,
i found the problem in the class: MethodMatcher =20

Before we add this code

                if (obj =3D=3D null ||=20

                        (desiredParamTypes[i].isAssignableFrom(objClass))
||

                      =20
(desiredParamTypes[i] =3D=3D Integer.TYPE && Integer.class.isAssignableFrom=
(objClass))
||

                      =20
(desiredParamTypes[i] =3D=3D Double.TYPE &&
Double.class.isAssignableFrom(objClass)) ||

                      =20
(desiredParamTypes[i] =3D=3D Long.TYPE &&
Long.class.isAssignableFrom(objClass)) ||

                      =20
(desiredParamTypes[i] =3D=3D Boolean.TYPE &&
Boolean.class.isAssignableFrom(objClass)) ||

                      =20
(desiredParamTypes[i] =3D=3D Character.TYPE &&
Character.class.isAssignableFrom(objClass)) ||

                      =20
(desiredParamTypes[i] =3D=3D Float.TYPE &&
Float.class.isAssignableFrom(objClass)) ||

                      =20
(desiredParamTypes[i] =3D=3D Short.TYPE &&
Short.class.isAssignableFrom(objClass)) ||

                      =20
(desiredParamTypes[i] =3D=3D Byte.TYPE &&
Byte.class.isAssignableFrom(objClass)))

              =20
{

                  =20
parameters.set(i, obj);

                  =20
matchCount++;

              =20
}

So, when the conversion used by the TypeMarshaller returns null then the pa=
rameter is added to be use in the method call by reflection


But with the new version:
if (objClass !=3D null && isAssignableFrom(desiredParamTypes[i],
objClass))              =20
{                  =20
// See if there's
an exact match before parameter is converted.                  =20
if (isAssignableFrom(desiredParamTypes[i],
param.getClass()))                      =20
exactMatchCount++;                   =20
if (convert) // Convert the parameter.                      =20
parameters.set(i, obj);                   =20
matchCount++;


              =20
}

The condition of the object is removed it should be (if (obj =3D=3D null ||=
(objClass !=3D null && isAssignableFrom(desiredParamTypes[i], objClass))) b=
ecause the condition to get the objClass is  currentMatch.convertedSupplied=
Types[i] =3D (obj !=3D null ? (objClass =3D obj.getClass()) : null);

So with the change of the current code the TypeMarshaller everytime that se=
nd null the ObjClass will be null and then the matchCount will no tbe updat=
ed and the parameter is not set! Causing the exception that this method don=
't exist.

Here is the full class from the version 3.2:http://grepcode.com/file/repo1.=
maven.org/maven2/com.adobe.blazeds/blazeds-core/3.2.0.3978/flex/messaging/u=
til/MethodMatcher.java
Chris, It is possible to make this change or is better to find a "local" so=
lution?
Thanks again in advance.
> From: christofer.dutz@c-ware.de
> To: users@flex.apache.org
> Subject: AW: Blaze DS 4.7.1
> Date: Wed, 26 Aug 2015 20:59:35 +0000
>=20
> Does this article of mine eventually help?
>=20
> https://dev.c-ware.de/confluence/display/PUBLIC/Fixing+the+mapping+of+
> null+values+for+numeric+types
>=20
> Chris
>=20
> ________________________________________
> Von: Mario Souza <mario.souza@vizexplorer.com>
> Gesendet: Mittwoch, 26. August 2015 22:48
> An: users@flex.apache.org
> Betreff: Re: Blaze DS 4.7.1
>=20
> You have a NaN value in Java if you're using the Double or Float=20
> http://docs.oracle.com/javase/1.5.0/docs/api/java/lang/Double.html#NaN
> http://docs.oracle.com/javase/1.5.0/docs/api/java/lang/Float.html#NaN
>=20
>=20
> I'm not sure but I think that BlazeDS serializes the AS3 Number.NaN to=20
> a Java Double type, then by reflection api, the BlazeDS can't find a=20
> method with this signature (String, Double) because your signature is=20
> a (String, Long).
>=20
> Change your method signature and make sure that you're sending the=20
> correct types from AS3.
>=20
>=20
> Regards.
>=20
>=20
>=20
>=20
> ---
> *Mario de Souza*
> UI Developer
> Website: www.vizexplorer.com
> Skype: vizexplorer-mariosouza
> M +6421 082 71135
> <http://www.vizexplorer.com/>
> Level 3, 54-56 Cambridge Terrace
> PO Box 19204, Wellington 6149
>=20
> *The information contained in this email may be private and/or=20
> confidential. It has been sent for the sole use of the intended=20
> recipient(s). If the reader of this message is not an intended=20
> recipient, you are hereby notified that any unauthorized review, use,=20
> disclosure, dissemination, distribution, or copying of this=20
> communication, or any of its contents, is strictly prohibited. If you=20
> have received this communication in error, please contact the sender=20
> by reply email and destroy all copies of the original message.*
>=20
>=20
> On 27 August 2015 at 04:03, Miguel Ferreira=20
> <miguel.cd.ferreira@hotmail.com>
> wrote:
>=20
> > zero and -1 have meaning in the business application.
> > The workaround is to pass a context object as argument.
> >
> > But, this kind of error dint exist before in the old version 3.2 of=20
> > BlazeDS.
> > I don't know why when is trying to call the remote function BlazeDS=20
> > don't find the correct signature.
> > I even try to have another method without the last parameter to=20
> > verify the behavior of it.
> > Maybe someone know how i can try to switch on the debugger of blazeDS.
> > Thanks for the help deepak. I am trying to see a general solution=20
> > because i have a lot of methods that use Long as an argument.
> > > Date: Wed, 26 Aug 2015 21:27:26 +0530
> > > Subject: Re: Blaze DS 4.7.1
> > > From: megharajdeepak@gmail.com
> > > To: users@flex.apache.org
> > >
> > > Is there any purpose of passing NaN ? You may instead try to pass=20
> > > a specific number say 0 or -1 in case of NaN.
> >
> >
 		 	   		 =20