Bugzilla – Full Text Bug Listing
| Summary: | [Webdoc] Event Specification for Java profiling is not current with its schema. | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Paul Slauenwhite <paulslau> |
| Component: | TPTP | Assignee: | Harm Sluiman <sluiman> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P2 | CC: | duncan, fernacolo, nmehrega |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | housecleaned460 | ||
| Bug Depends on: | |||
| Bug Blocks: | 107521 | ||
|
Description
Paul Slauenwhite
I started to build an EMF model for the events, once we clean up this document I can regen that model and provide samples on how to use it. I think we can do this in 4.2 i3, I will provide the new elements for 4.2 by then. We might need to rename this schema as we use this schema in non-JVMPI scenarios. Later I would like to move this schema file to the models plugin. As per Marius' comment, he will provide the updated schema consistent with the actual model/loader support (possibly automatically generated from his emf model). Once that's done, he's agreed to update the web docs (schema and event specification) accordingly. The obsolete dtd is expected to be retired at that point (ie: no longer published). Note that the event specification currently references the dtd extensively and will need to be changed to reference the schema instead. This work is being done under the Platform.Model component (rather than the Platform.Agents.JVMPI component) because the JVMPI agent is not the only profiling/tracing agent which generates elements according to this schema. The schema (and the documentation/publishing thereof) is therefore deemed to belong to the model/loader. With Marius' agreement, I am transferring this to the Platform.Model component and targetting it to 4.2i3. It's expected to be permissible to do this work in 4.2i3 because it's effectively a doc change. Beware: There was some confusion yesterday about an updated schema being currently available under the Platform.Model tree in cvs (specifically in platform/org.eclipse.tptp.platform.models/src-trace/model/traceEvents.xsd). It turns out that that schema is more current than the web-published one but it is *not* fully up-to-date (it was produced under bug 102152). In particular it appears that it does *not* fully specify support for parameters or return values. In any case, that file should ultimately be updated or retired as part of this work as well. Consider changing the http://www.eclipse.org/tptp/platform/documents/resources/profilingspec/trace.xsd link for the schema on the web site to point to the generated schema stored in the model to reduce maintenance. Also, the new schema should be well commented, similar to the existing http://www.eclipse.org/tptp/platform/documents/resources/profilingspec/trace.xsd schema. Consider generating the Event Specification for Java profiling (http://www.eclipse.org/tptp/platform/documents/resources/profilingspec/XML4Profiling.htm) document from the commnented schema. (In reply to comment #4) Consider using XSD2HTML (http://crism.maden.org/consulting/pub/xsl/xsd2html.xsl to) or something similar for converting the schema to HTML. *** Bug 135719 has been marked as a duplicate of this bug. *** (In reply to comment #6) Bug 135719 calls attention particularly to the new aggregating agent elements/atributes which are among the ones that need to be covered by this work. Moved to 4.2 i4, requires only web updates. Marked as P2 for further investigation and approval. As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. Since this defect is more than 2 years old, it may be no longer relevant. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this defect is resolved as WONTFIX. If this defect is still relevant and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open. Closing. |