Hi,
>From what I've seen, the object in your ObjectMessage should follow the same
>rules as what any Seam Remoting @WebRemote method would return (Section 19.6
>of the doco) -- ie: keep it as a simple JavaBean so you can access the
>serialized state from javascript using properties. I don't think a Java
>Properties object will work. You could use Firebug in firefox to debug the JS
>and view what Seam is returning inside the Seam.Remoting.ObjectMessage if you
>really want to try it.
Also from looking at Seam's remote.js, I think you call ".value" or
"getValue()" on the ObjectMessage, not ".object/getObject()" as the
documentation says.
| Seam.Remoting.ObjectMessage = function()
| {
| this.value = null;
|
| Seam.Remoting.ObjectMessage.prototype.getValue = function()
| {
| return this.value;
| }
|
| Seam.Remoting.ObjectMessage.prototype.setValue = function(value)
| {
| this.value = value;
| }
| }
|
Daniel.
"dkane" wrote : No way ?
|
| I could of course serialize Object to string and use TextMessage instead.
But there are some other subscribers already targeted to ObjectMessage.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4048070#4048070
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4048070
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user
