-
Enhancement
-
Resolution: Unresolved
-
P4
-
fx2.0
-
None
PERF-132 updated the launch time logging code, but it's not an ideal solution. For instance, custom parameter handling code was added on the deploy side, instead of the code being isolated to the PerformanceTracker. A more desirable fix for PERF-132 could be written if we had parameter access from the library level.
This could be provided either directly (e.g. ParametersImpl.params.getAll()) or indirectly via access to an Application object (e.g. Application.getCurrentApplication() -> theApp.getParameters()).
It seems to me a non-public method would be sufficient - application developers already have access to their own Application object.
- relates to
-
JDK-8100656 Allow Application to get access to startup parameters.
- Resolved