On Fri, Jun 26, 2009 at 10:44 PM, Simon Nash<[email protected]> wrote: > Simon Laws wrote: >>> >>> The service has a forward <binding.ws/> and a callback <binding.ws/>. >>> These have no "name=" attribute, so they both default to the name of >>> the service. SCA doesn't permit two bindings with the same name, and >>> this is why you get the warning. The {2} in the message is a bug in >>> the 1.3.1 message template, and has been fixed in the latest code. >>> >> >> Interesting. I didn't realize that the it checked across both forward >> and callback binding collections to determine uniqueness of binding >> name. >> >> Simon >> >> > I discovered this when doing some experiments with callback bindings > recently. Tuscany works this way, and the SCA spec doesn't say whether > or not the scope of callback binding name uniqueness should be distinct > from the forward bindings. > > If anyone feels that this should be changed, I would be happy to raise a > spec issue. It does seem to be a bit of a pitfall that catches people out. > > Simon > >
It does sound like it should be changed to me. From what the user is saying this is actually running fine so its doesn't seem good to require them to add a bit more xml config for no other purpose than to avoid an unnecessarily strict name check warning message. ...ant
