APIReview182772

Participants: Petr Suchomel [PS], Jarda Tulach [JT], Petr Hejl [PH], Tomas Hurka [TH], Jirka Sedlacek [JS], Vince Kraemer [VK], Denis Anisimov [DA]

TCRs & TCAs List

TCR: Performance - do not load classes until profiler/profiler j2ee usage.

TCR: It must work with Maven as it is now. Maven requests should not break the API in future.

TCR: Project level profiler registration.

TCA: Use annotations (compile time) to simplify registration.

Discussion

JT: TCR: Performance - do not load classes until profiler/profiler j2ee usage.

JT: TCA: Use annotations (compile time) to simplify registration.

JS: Soon for implementation details. Intial meeting for high level goals. We should define purpose of the API. It's about improvement of J2EE profiler integration

  • not just the netbeans profiler, but other profiler as well
  • to clean up and improve api

JS: No new modules are introduced.

Discussion:
VK: Which other profiles (than NetBeans) have you used to test the API/SPI?
DA: No other profiler implementation.

TH & JS: TCR: It must work with Maven as it is now. Maven requests should not break the API in future.

Discussion:
PS: Is there use case for more than one profiler?
TH: Yes, in future. User can choose. The question is on what level the profiler configuration will be possible. Java EE only discussion now. The next step would be Java SE etc. The future changes should not break the API compatibility.

Discussion:
PS: Profiler by ID is dubious. Should it be connected to project?
TH: Suggests profiler in project lookup. With global registration the lookup has to be searched by ID.
DA: Ant task supports global profiler or particular profiler.
VK: There is no UI to change profiler A to profiler B on project. Premature to worry about.
PH: The different profilers should be supported or there should be possibility to add it in compatible way.
TH: There is option to drop this part of the API.
JS: We are not sure if we are able to add it in compatible way. This would point to usage of friend API.
PS: TBD later.

Discussion:
TH: Should be profiler registered on global or per project level?

TH: TCR: Project level profiler registration.

Discussion:
TH: Method/class naming problems in current implementation. Looks like the implementation won't work with multiple profilers.
DA: No reason to change anything. It was discussed in IZ.

Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo