sebersole · September 19, 2013 14:27
diff --git a/gistfile1.txt b/gistfile1.txt
 Specifically here the phrase "is not recognized" is in question. In our opinion there are 2 problems with the JPA provider accepting such properties at the EntityManager level:

 * Unnecessary growth of the map used to hold these properties
 * Misleading feedback when/if EntityManager#getProperties() is later called (here it would look like some BV config is in use when it is not).

 I understand that the wording in the javadoc makes what the TCK does allowable, but in my opinion the intent is incorrect and we ask that this be changed. There are other properties that actually have meaning at the EntityManager level that could be used to test this instead.
	Specifically here the phrase "is not recognized" is in question. In our opinion there are 2 problems with the JPA provider accepting such properties at the EntityManager level:

	* Unnecessary growth of the map used to hold these properties
	* Misleading feedback when/if EntityManager#getProperties() is later called (here it would look like some BV config is in use when it is not).

	I understand that the wording in the javadoc makes what the TCK does allowable, but in my opinion the intent is incorrect and we ask that this be changed. There are other properties that actually have meaning at the EntityManager level that could be used to test this instead.
No results found