Hi,
On 01/26/2013 10:59 AM, Sivakumar Thyagarajan wrote:
> I added an EoD optimization in Section 18.9.2 (in the new draft) that I
> realized later I did not discuss with the EG earlier. Sorry about that.
>
> The uniqueness constraints of AdministeredObjects since Connectors 1.6
> is interface *and* class name. Since these resource definition
> annotations are meant for ease of develoeprs, I think that in most
> cases, there would be a admin object class with one interface, and so
> specifying the interface also is superflous.
>
> So I have made the specification of the interface optional in
> @AdministeredObjectDefinition, as the application server can handle this
> in those scenarios. The specification of interface name is only required
> if the admin object has more than one interface in 18.9.2.
>
> What do you think? Would there be any other issues with this?
Agreed.
The interface value can be left out as default.
Best regards,
Jesper