-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide constants for properties #139
Comments
@glassfishrobot Commented |
@glassfishrobot Commented |
|
This would be a very good thing to do. |
1. add constructor taking name, and make name immutable 2. clarify rules for vendor subclasses 3. add constant property names 4. improve javadoc see jakartaee#481, jakartaee#139
#482 adds a list of configuration properties to This addresses at least the first requested item, which is, IMO, the most acute need. In other work (#383) we've already added typesafe methods for specifying timeouts, cache modes, and the "load" graph. The only standard hint not covered by all the above, unless I've missed something, is the infamous |
There are a lot of available properties, each one applicable to specific scenarios:
Those properties are scattered trough the spec and it's difficult to find all of them and to know which one applies to which scenario.
A simple yet very handful addition would be a class that groups all the properties and specifies its applicability in its JavaDoc.
Hibernate already does something like this: https://github.com/hibernate/hibernate-orm/blob/0a2a5c622e3eb30724e80bc8661c0ac55ebfb2be/hibernate-core/src/main/java/org/hibernate/cfg/AvailableSettings.java
Affected Versions
[2.1.1]
The text was updated successfully, but these errors were encountered: