Community
Participate
Working Groups
Provide rule editor extension point to support adding components dynamically to UI. In this way, GLA component writers can have their components available in the UI for users to select while using the rule editor.
The goal here is to make it easier for GLA users to use the GLA editor to create adapter files with the components (likely need to support this functionality for sensors and outputters only) they want to use. They should be able to select a sensor or outputter by name without having to know the details of implemenation class name and required property names. These details will be provided in the extension point and the GLA editor will use them to prefill the fields in the adapter file when the component is added.
update priority per Chris's request
Theme: Design for Extensibility: Be a Better Platform, Appealing to the Broader Community
update component
*** Bug 119067 has been marked as a duplicate of this bug. ***
Move back to P1 per Chris's request
Candidate for 4.2
The goal here is to make it easier for GLA users to use the GLA editor to create adapter files with the components (likely need to support this functionality for ALL the GLA components) they want to use. They should be able to select a sensor, extractor, formatter or outputter by name without having to know the details of implementation class name and required property names. These details will be provided in the extension point and the GLA editor will use them to prefill the fields in the adapter file when the component is added.
A new extension point is now available to customize context and component creation. The extension allows you to define a complete context definition by grouping together the adapter components to be run for the selected context See below the description of this extension point : Identifier: org.eclipse.hyades.logging.adapter.ui.glaComponent Since: TPTP 4.2 Description: Use this extension point to create a custom component so that the user can select a sensor, extractor, formatter or outputter by name without having to know the details of implementation class name and required property names. These details will be provided in the extension point and the GLA editor will use them to prefill the fields in the adapter file when the component is added. Configuration Markup: <!ELEMENT extension (component+)> <!ATTLIST extension point CDATA #REQUIRED name CDATA #IMPLIED id CDATA #IMPLIED> point - a fully qualified identifier of the target extension point name - an optional name of the extension instance id - an optional identifier of the extension instance <!ELEMENT component EMPTY> <!ATTLIST component name CDATA #REQUIRED description CDATA #IMPLIED role CDATA #REQUIRED class CDATA #REQUIRED version CDATA #IMPLIED loggingLevel CDATA #IMPLIED id CDATA #REQUIRED parent CDATA #IMPLIED> name - the name of the component description - an optional description of the component role - the component role. Valid values are sensor, messageExtractor, parser, formatter, messageFilter, cbeFilter, outputter class - the name of the class implementing this component version - the version of this class loggingLevel - logging level for this component id - the id of the extension point parent - an optional parent component Examples: <extension point="org.eclipse.hyades.logging.adapter.ui.glaComponent"> <component id="org.eclipse.hyades.logging.adapter.ui.BasicContext" name="%10" description="%11" class="org.eclipse.hyades.logging.adapter.impl.BasicContext" version="1.0" role="context" loggingLevel="30"/> <component id="org.eclipse.hyades.logging.adapter.ui.OSSensor" parent="org.eclipse.hyades.logging.adapter.ui.BasicContext" name="%3" description="%2" class="org.eclipse.hyades.logging.adapter.sensors.SingleOSFileSensor" version="1.0" role="sensor" loggingLevel="30"/> </extension>
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.
