Serializing a Double/Number

Question

This seems to be a bug in BlazeDS, but hopefully not. I'm trying to serialize between a Number and a double, but Flash seems to be trying to link the Number to an int, causing it to fail.
Here's my source, so someone can try it out:
- FlashTest.mxml ---
<?xml version="1.0" encoding="utf-8"?>
<s:Application
xmlns:fx="http://ns.adobe.com/mxml/2009"
xmlns:s="library://ns.adobe.com/flex/spark"
xmlns:mx="library://ns.adobe.com/flex/mx"
initialize="init()"
>
<fx:Script>
import Modifier;
</fx:Script>
<fx:Script source="FlashTest.as"/>
<fx:Declarations>
<mx:RemoteObject id="rObject" destination="RObject">
<mx:method name="getModifier" result="rObject_getModifier(event)" fault="rObject_fault(event)" />
</mx:RemoteObject>
</fx:Declarations>
</s:Application>
- Modifier.as ---
package {
[Bindable]
[RemoteClass(alias="Modifier")]
public class Modifier {
private var _uid:Number;
private var _type:int;
private var _value:int;
public function get uid() : Number {
return _uid;
public function set uid(uid:Number) : void {
_uid = uid;
public function get type() : int {
return _type;
public function set type(type:int) : void {
_type = type;
public function get value() : int {
return _value;
public function set value(value:int) : void {
_value = value;
- FlashTest.as ---
import mx.rpc.events.*;
import spark.components.*;
import mx.collections.ArrayCollection;
private var login:TextInput;
private var count:int = 0;
private var mod:Modifier;
private var objects:ArrayCollection;
public function init() : void {
login = new TextInput();
login.width = 800 * 0.8;
login.height = 30;
login.x = (800 - login.width) / 2;
login.y = 10;
login.text = "Hello world!";
login.addEventListener(KeyboardEvent.KEY_DOWN, grabEnter, false);
addElement(login);
public function grabEnter(evt : KeyboardEvent) : void {
if (evt.keyCode == 0xd) { // Pressed enter
rObject.getModifier();
public function rObject_getModifier(event:ResultEvent) : void {
mod = Modifier(event.result);
login.text = "UID = " + mod.uid + " & type = " + mod.type + " & value = " + mod.value;
public function rObject_fault(fault:FaultEvent) : void {
login.text = fault.fault.faultString + " " + fault.fault.faultDetail + " " + fault.fault.message;
- RObject.java ---
import javax.persistence.*;
import javax.ejb.*;
import javax.naming.*;
import java.util.List;
import java.util.ArrayList;
public class RObject {
private IFacade f = null;
public RObject() {
try {
Context context = new InitialContext();
f = (IFacade)context.lookup("Facade/local");
catch (NamingException e) {
e.printStackTrace();
public Modifier getModifier() {
return f.getModifier();
- IFacade.java ---
import javax.ejb.*;
import javax.persistence.*;
import org.jboss.ejb3.annotation.*;
@Local
public interface IFacade {
public Modifier getModifier();
- Facade.java ---
import javax.ejb.*;
import javax.persistence.*;
import org.jboss.ejb3.annotation.*;
@Stateless
public class Facade implements IFacade {
@PersistenceContext(unitName="RPersist")
EntityManager em;
Modifier modifier = null;
public Facade() {}
public Modifier getModifier() {
if (modifier == null) {
modifier = em.find(Modifier.class, 1);
if (modifier == null) {
modifier = new Modifier(1.0, 42, 13);
em.persist(modifier);
else {
modifier.setValue(55);
return modifier;
- Modifier.java ---
import java.io.Serializable;
import javax.persistence.*;
import javax.ejb.*;
@Entity
public class Modifier implements Serializable {
@Id
@Column(name="UID")
private long uid;
@Column(name="ModType")
private int type;
@Column(name="ModValue")
private int value;
public Modifier() {}
public Modifier(int t, int v) {
type = t;
value = v;
public java.lang.Long getUid() {
return uid;
public void setUid(java.lang.Long l) {
uid = l;
public int getType() {
return type;
public void setType(int t) {
type = t;
public int getValue() {
return value;
public void setValue(int v) {
value = v;

Answer 1

I reported this as a bug a few days ago, but it looks like the default assignee for it hasn't done anything since June which worries me that it might be sitting in some unseeable place -- e.g. the guy quit but his account still exists getting assigned bugs. If one of the BlazeDS developers is on here, could you verify that the bug is assigned to someone who can decide whether to accept or ignore the issue?
https://bugs.adobe.com/jira/browse/BLZ-589