Entity EJBs always have to have a primary key, but if the key is an object of and existing Java class (such as java.lang.String) you don't have to wrap it in a custom primary key class. There is a slight difference in the ejb-jar.xml depending on whether your key is an object or a primary key class and a lot of systems don't detect improper configuration, so use caution.
One of the most odious afflictions that Business has inflicted on the modern English language is "pro-active". Most of the time it's simply redundantly used in place of the simple old word "active". And a good deal of the rest of the time it means "You're not overworked enough yet, so go out and find more!"
0
