This approach sounds good to me. I'd like to suggest one small
addition to the final else clause, based on the following spec quote:
Java SCA Annotations and APIs spec: 1531
Complex data types exchanged via remotable service interfaces must be
compatible with the marshalling technology used
Simon Nash wrote:
This approach sounds good to me. I'd like to suggest one small
addition to the final else clause, based on the following spec quote:
Java SCA Annotations and APIs spec: 1531
Complex data types exchanged via remotable service interfaces must be
compatible with the
Giorgio Zoppi wrote:
2007/12/5, Jean-Sebastien Delfino [EMAIL PROTECTED]:
Jean-Sebastien Delfino wrote:
Some answers after researching the spec docs:
Raymond Feng wrote:
Hi,
I think this issue needs to be brought up at the spec level.
Basically, the following have to be clarified:
1) What
We had some discussions before on this list how the pass-by-value should be
enforced. IIRC, the conclusion is that it would be a joint effort between
the implementation/binding type and the runtime. In most cases, bindings
representing remote protocols marshal/unmarshal the data on the wire.
Great!
Giorgio, if I understand correctly, the above scheme will help you
trigger the XStream databinding for objects that implement the
XStreamable interface you've defined.
Yes. I use it also for serializing Jobs, but I'm going to change this.
I feel that too much xml
is compute extensive.
Hi,
What we have today is mostly in line with your proposal. Only a few twicks
are needed.
1) If the data type is recognized by a known databinding, for example, SDO
or JAXB, the databinding specific-copy is used. For SDO, it will be SDO
CopyHelper.copy and for JAXB, it will be
2007/12/5, Jean-Sebastien Delfino [EMAIL PROTECTED]:
Jean-Sebastien Delfino wrote:
Some answers after researching the spec docs:
Raymond Feng wrote:
Hi,
I think this issue needs to be brought up at the spec level.
Basically, the following have to be clarified:
1) What interfaces
Jean-Sebastien Delfino wrote:
Some answers after researching the spec docs:
Raymond Feng wrote:
Hi,
I think this issue needs to be brought up at the spec level.
Basically, the following have to be clarified:
1) What interfaces are qualified to be remotable?
2) What are the characteristics
Some answers after researching the spec docs:
Raymond Feng wrote:
Hi,
I think this issue needs to be brought up at the spec level. Basically,
the following have to be clarified:
1) What interfaces are qualified to be remotable?
2) What are the characteristics of the input/output types for
