I've just created the test case and reproduced the behaviour (I won't
say problem because I think perhaps what we recommend today might be
the real problem). I tried something which I thought I'd already
attempted and it worked. So here's the explanation.
It seems having interfaces changes
On 8 Sep, 09:30, Graham Charters [EMAIL PROTECTED] wrote:
Just a quick status update...
I've done the code to optionally allow an interface to be specified
and tested this independent of a protocol binding and all works fine.
Unfortunately, when called from a remote invocation, the
Just a quick status update...
I've done the code to optionally allow an interface to be specified
and tested this independent of a protocol binding and all works fine.
Unfortunately, when called from a remote invocation, the classexists
tests for the service implementation fails.
It sounds like we may have consensus. To summarise:
1. We should add the ability to specify an optional interface for the
service on the @service annotation (e.g. @service
MyServiceInterface). This would only be used to limit the methods
exposed by the service, so we would not look for any
Hi Graham
Some more comments in line...
On 31 Aug, 11:26, Graham Charters [EMAIL PROTECTED] wrote:
Hi Simon, thanks for the rapid comments. Here's my thoughts on the
two issues you identified:
1/ What should SCA do if it finds a method without annotations, i.e.
no type information
Comments inlined below...
On 31 Aug, 11:35, [EMAIL PROTECTED] wrote:
Hi Graham
Some more comments in line...
On 31 Aug, 11:26, Graham Charters [EMAIL PROTECTED] wrote:
Hi Simon, thanks for the rapid comments. Here's my thoughts on the
two issues you identified:
1/ What should
Actually after a second glance, I see all annotations are still set in
the class. It probably wouldn't make any sense to have SCA parse
annotations in the interface.
Matt
On 31 Aug, 06:20, Graham Charters [EMAIL PROTECTED] wrote:
Comments inlined below...
On 31 Aug, 11:35, [EMAIL
