#765
  • Created on
    2011-04-08 12:00
  • Reported by
    spacedragon
  • Status
    Fixed
  • Priority
    Normal (3)
  • Assigned to
    viktorklang
  • Milestone
    2.0-M1
  • Plan Level
    -
  • Due Date
    -

Attachments

Related Tickets

Add new subtask or bug

Typed actor message serialization bug?

typed actor will always use default java
serialization way because in MessageSerializer.scala :

// code in serialize method:
if (message.isInstanceOf[Serializable.JavaJSON]){
.......

}else{
....
}

the message here is supposed to be the augument of methods in
TypeActor. but the typed actor will wrap it's method arguments to a
Object[]{arg1,arg2,...}. So the above code will always go to else clause.
User picture
  on 2011-04-12 13:51 *
By viktorklang
What is the proposed solution?

This is not a bug per se.
User picture
  on 2011-04-12 13:51 *
By viktorklang
Moving this forward to 2.0 since TypedActor will get some love there.
User picture
  on 2011-04-12 13:52 *
By viktorklang
Milestone changed from 1.1 to 2.0
User picture
  on 2011-06-06 00:28 *
By viktorklang
Status changed from New to Accepted
Awaiting Debasish to push new serialization into master.
User picture
  on 2011-06-06 00:31 *
By viktorklang
Assigned to set to viktorklang
User picture
  on 2011-06-17 12:02 *
By viktorklang
Assigned to changed from viktorklang to -none-
Status changed from Accepted to New
User picture
  on 2011-07-15 14:24 *
By viktorklang
Assigned to set to viktorklang
Status changed from New to Fixed
Fixed in master with new TypedActor implementation. Will use individual serializers per method parameter value
User picture
  on 2011-12-15 00:54 *
By viktorklang
Milestone changed from 2.0 to 2.0-M1
Updating tickets (#684, #883, #886, #995, #1017, #968, #969, #973, #1002, #1016, #1021, #1035, #1048, #1119, #1156, #1451, #231, #470, #595, #599, #639, #655, #687, #691, #692, #693, #724, #728, #729, #749, #751, #755, #765, #766, #767, #769, #770, #771, #772, #784, #785, #807)