Details
-
Task
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
1.2.3, 2.0.3, 1.1.3
-
None
Description
the following steps are important improvements scheduled for the 4th release.
(some of them have to be tested carefully. so they won't get into the 3rd release.)
part #1:
create a wiki which provides tips for tweaking the performance.
e.g. if users just use the bv integration it's possible to deregister the ValidationInterceptor.
provide information how to optimize the DefaultValidationParameterExtractor
part #2:
in release 4 extval will switch from commons-logging to jul
classes which get instantiated quite often - e.g.:
DefaultPropertyInformation
DefaultValidationParameterExtractor
ExtValELResolver
ExtValGenericRendererWrapper
ExtValRendererProxy
ExtValRendererWrapper
MetaDataEntry
should use static loggers.
part #3:
optimize the combination with the property validation module:
e.g. ExtValContextInternals creates a new instance of InformationProviderBean if there is no custom implementation.
if possible it should be cached in the applicationMap (like the custom impl.) to avoid checking for custom impl. the next time.
that might be incompatible with some mechanisms which are invoked lazily + maybe it won't be needed after all other tweaks.
DefaultValidationStrategyFactory invoked by ValidationInterceptor doesn't find validation strategies e.g. for bv constraints (for sure).
so it tries to find them every time as soon as such constraints are found. so null should be stored in the cache for the current metaDataKey
part #4:
after the improvements mentioned above, the property validation module will be tweaked automatically.
but there are some parts of the bv integration which need further analysis.
part #5:
check and improve add-ons - see: