Hi Patrick,I don't think there would be an issue with calling it unitName or persistenceUnitName, as in getUnitName() or getPersistenceUnitName(). It will be common for people to try to figure out what the Id property from a Configuration really means so the more help we give them the easier it will be to remember.
openjpa.unitName openjpa.persistenceUnitName Maybe I'm missing something obvious... Craig On Nov 9, 2006, at 2:19 PM, Patrick Linskey wrote:
Hi,It's useful in a number of places to get an identifier for a particularConfiguration. For example, as we discussed a few months ago, it would be useful if the logging subsystem automatically wrote the persistenceunit's ID along with log messages if no such ID was specified in the logconfiguration. Any objections to such an addition? In a JPA environment, this would correspond to the persistence unit's unitName attribute.Any suggestions for a better name than openjpa.Id for the property? Thiswould result in an OpenJPAConfiguration.getId() method call that returned a String. -Patrick -- Patrick Linskey BEA Systems, Inc.______________________________________________________________________ _ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return thisby email and then delete it.
Craig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp!
smime.p7s
Description: S/MIME cryptographic signature
