Seems reasonable.
Regards,
Fred Rowe
WebSphere Architect
Senior Software Engineer
IBM Software Group
frowe_at_us.ibm.com
Sivakumar Thyagarajan <sivakumar.thyagarajan_at_oracle.com>
01/26/2013 10:59 AM
Please respond to
jsr322-experts
To
jsr322-experts_at_connector-spec.java.net
cc
Subject
[jsr322-experts] An optimization covered in 18.9.2 of the new draft
Hello experts
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?
Thanks
--Siva.