[3.1 TCK Challange] entity classes used by testcase does not conform to java bean standard

[javasmithy]

in files jpa/core/entityManager/Order.java and jpa/core/entityManager2/Order.java have methods getdescription and setdescription which doesn't conform to java been specification.

[gavinking]

Hi, I agree that that is highly strange, and I can't really explain why the test is written that way.

It would be OK to remove or rename these accessor methods.

On the other hand, this isn't actually disallowed by the spec. Per spec, this is just a transient (non-persistent) field and two methods. The description simply doesn't fulfill the requirements to be a persistent property.

So, two things:

1. I don't see this as an actual bug in the TCK, but I would accept a pull request to change it, because I doubt it's making any actual useful contribution to what that test is testing.
2. I would like you to please use your real name and make explicit your affiliation when reporting TCK challenges. If you work on datanucleus, then that's great, but it's important for us to know things like that when dealing with TCK challenges.