Geek asks and answers

Why does Java EE 6 require equals () and hashCode () to be implemented for Resource Adapters?

I am working on upgrading code from JBoss 5.1 to JBoss 7.1, and it fails if these methods are not explicitly implemented in resource adapters. I understand the concept of everyone and I know about the contract between them. I do not ask how to implement them or what they mean. I specifically ask why they MUST be implemented for Java EE 6 code (in this case, JBoss AS 7.1).

Is there a good reason to think about them or is it simple enough:

boolean equals(Object obj) { return super.equals(obj) ; }
int hashCode() { return super.hashCode() ; }
+5
source share
1 answer

I think this is because of the following

checkout ManagedConnectionFactory here.

. equals() hashCode(). , java, , , . , .

ManagedConnectionFactory .

, JCA 1.6,

A resource adapter must provide implementations of the following interfaces:

javax.resource.spi.ManagedConnectionFactory
javax.resource.spi.ManagedConnection
javax.resource.spi.ManagedConnectionMetaData

1.5

JCA 1.6, , .

, . , , "" factory.

, , JCA 1.5, 1.6

+1

More articles:


All Articles