On Aug 4, 2006, at 4:05 PM, Jim Marino wrote:
A while back, we decided to express operations using
java.lang.Method. People have raised this as an issue when dealing
with implementation types that may not use Java interfaces to
represent services. This has also been problematic in dealing with
Java metadata, as it forces knowledge of particular Java
annotations deep in the runtime (e.g. @OneWay or @Callback when
creating a TargetInvoker, which will really be problematic for
things like async Javascript or Groovy).
I'd like to solve this ASAP. Any ideas/proposals/requirements
people would like to raise?
I think this may need to hook into the databinding framework as well.
j.l.Method represents the contract in Java terms which poses a
problem when we want to represent that the first argument is an
InputStream containing a XML instance (or a byte array containing an
MRI image or something). We need a way to indicate that we have both
physical and logical forms.
I don't know what that is yet, just adding a requirement :-)
--
Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
