OperationSelectors would seem more appropriate for defining how
protocol messages map to service implementation operations. Wire
format seems more suited to transforming content types into the
arguments the implementation operations require.
Without a custom operation selector, i.e. in the default case, the
mapping between atom/http operations must be specified somehow.
Several approaches are floating around
- convention
Assume that methods will be called get, put etc. I think we
already support this
- annotation
As per JAX-RS. We would need some way of getting this information
into the binding
- a specific data interface
As per our current data interface. I believe this can still be
used over other bindings
With customization of the operation selection we could either go with
something like Ant is suggesting
<operationselection.atomcustom userclass="some.pkg.SomeClass"/>
And/or something more declarative in a similar way that the JMS spec
deals with this
<operationselection.atomdefault>
<operation name="GET" nativeOperation="myGet"/>
etc
</operationselection.atomdefault>
With binding.atom is the uri of the binding always the path to a collection?
Simon
