On 10/12/11 20:18, Jeff Wang wrote:
Ok, finally found out where the bug is.  The key was in the line:

at 
com.myapp.data.Base$JaxbAccessorM_getId_setId_java_lang_Object.set(MethodAccessor_Ref.java:56)

I actually had a Base data object like so:
@MappedSuperclass
abstract public class Base<K>  implements Serializable {
<other fields and methods deleted>
        public abstract K getId();
        public abstract void setId(K id);       
}

The expedient of changing K to Long (all my currently implemented
objects have Long as Id) caused both the client side receiving and the
server side streaming to work just fine.  Well, it now returns "id" :
[3, 3], which is at least usable...

I'm not sure whether there's a way to get around it or it is an issue
with Jettison, but at least I'm able to get forward.  thanks!

If you can help me with reproducing it then I can try to investigate, send me please a simple jaxb bean code only and I can proceed from there

Sergey


Jeff

Reply via email to