Re: Dynamic invocation vs. late/dynamic binding

Hi Mark,

> Late/dynamic binding means being able to manipulate squares and circles
> with the Shape interface.  Dynamic invocation means being able to
> construct, for example, a "displaySquare" message without compile-time
> knowledge of the full Square interface.

That's fine - WSIF can handle that using something called JROM we
created (see alphaWorks again) to represent arbitrary schema typed
values. 

Clearly, in the absence of magic the information about the interface
(namely the data type defs) is needed at runtime at least (possibly
using xsi:type), so once that's available you're on easy street.
 
> The former enables a client written to access Shape objects, to later
> access triangles, ovals, hexagons, you name it.  The latter doesn't.

I guess we're back to the REST vs. WS debate; your program cannot
manipulate those shapes in a meaningful way without an understanding
of what an oval is vs. a square. In the BPEL scenario the BPEL process
would need to understand all the shapes and then the underlying
infrastructure of WSIF/JROM can handle everything just fine.

Sanjiva.