0003801: hessian with enum

Viewing Issue Advanced Details [ Jump to Notes ]

[ View Simple ] [ Issue History ] [ Print ]

Category

Severity

Reproducibility

Date Submitted

Last Update

0003801

[Hessian]

minor

always

12-07-09 08:13

07-04-13 01:26

Reporter

alex

View Status

public

Assigned To

Priority

normal

Resolution

open

Platform

Status

new

Projection

none

OS Version

ETA

none

Fixed in Version

Product Version

4.0.2

Product Build

Summary

0003801: hessian with enum

Description

reported by fil512 (forum.caucho.com)
Steps to reproduce in java 5:
1. create an enum (just a plain old enum, nothing fancy)
2. create a class that uses this enum
3. create a list of instances of these classes.
4. try to pass this list back as a return value from a method accessed through hessian spring remoting.

I've narrowed the bug down to the following very specific trigger conditions.
The list must contain at least 3 items.
The first two items shall have the same value for the enum.
The third item shall have a different value for the enum.

The error is that it is not able to assign null to the enum field.

The general condition that triggers this is any list of objects that have enum fields where somewhere down the list the enum value changes. As soon as the object with the different enum value is hit, you get the error.

I have tried about 4 different versions of caucho hessian and they all had this same error. Interestingly, when I tried burlap, I still got a hessian exception but the exception was that it couldn't assign a java.sql.TimeStamp to the enum value which is weird since I don't use java.sql.TimeStamp anywhere--I'm guessing it's trying a bunch of different strategies and just reporting failure on the last strategy.

Steps To Reproduce

Additional Information

Steps to reproduce in java 6:
1. create an enum (just a plain old enum, nothing fancy)
2. create a class that uses this enum
3. create a list of instances of these classes.
4. try to pass this list back as a return value from a method accessed through hessian spring remoting.

I've narrowed the bug down to the following very specific trigger conditions.
The list must contain at least 3 items.
The first two items shall have the same value for the enum.
The third item shall have a different value for the enum.

The error is that it is not able to assign null to the enum field.

The general condition that triggers this is any list of objects that have enum fields where somewhere down the list the enum value changes. As soon as the object with the different enum value is hit, you get the error.

I have tried about 4 different versions of caucho hessian and they all had this same error. Interestingly, when I tried burlap, I still got a hessian exception but the exception was that it couldn't assign a java.sql.TimeStamp to the enum value which is weird since I don't use java.sql.TimeStamp anywhere--I'm guessing it's trying a bunch of different strategies and just reporting failure on the last strategy.

Attached Files

Relationships

Notes
(0006282) sdeleuze 07-04-13 01:26	Same issue here with Hessian 4.0.7.

Issue History
Date Modified	Username	Field	Change
12-07-09 08:13	alex	New Issue
12-10-09 12:46	fil512	Issue Monitored: fil512
01-06-10 15:55	ferg	Project	Resin => Hessian
02-15-12 10:05	babasmith	Issue Monitored: babasmith
07-04-13 01:25	sdeleuze	Issue Monitored: sdeleuze
07-04-13 01:26	sdeleuze	Note Added: 0006282

Mantis 1.0.0rc3[^]

35 total queries executed.
29 unique queries executed.