Bug 104281 - Update GLA docs to indicate Time Format can be used in Extended Data Element rules
Summary: Update GLA docs to indicate Time Format can be used in Extended Data Element ...
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: TPTP.monitoring (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P1 normal (vote)
Target Milestone: ---   Edit
Assignee: Alex Nan CLA
QA Contact:
URL:
Whiteboard: closed460
Keywords: Documentation, plan
Depends on:
Blocks:
 
Reported: 2005-07-18 17:03 EDT by Dave Smith CLA
Modified: 2010-06-03 15:10 EDT (History)
5 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dave Smith CLA 2005-07-18 17:03:16 EDT
If I specify Time Format for the rule for the values element of an Extended 
Data Element, the value does not get parsed and a GLA warning message is 
logged.  Here is the warning message:

"IWAT0351W Common Base Event formatter N36C36700F8511D88000A31D7605087A has 
received an exception when processing extendedDataElements - java.lang.Long."

Extended Data Element values can be of type "dateTime". Hence the Time Format 
attribute of the substitution rule should be available and processed correctly 
for values of Extended Data Element.

To fix this the CBEFormatter must be able to process a Long value for the 
values attribute of ExtendedDataElement.
Comment 1 Dave Smith CLA 2005-07-18 17:14:01 EDT
The CBEFormatter class need to be changed to handle a Long value for the values 
attribute of ExtendedDataElement.  Using the Time Format field generates a Long 
value for the Date which then needs to be converted to a dateTime string.  The 
values attribute is then set with the dateTime string.

The GLA documentation needs to be updated for this new capability.  It 
currently says the Time Format is only used for the creationTime element.
Comment 2 Dave Smith CLA 2005-07-20 12:07:03 EDT
Deferring this to 4.2
Comment 3 Dave Smith CLA 2006-06-05 10:31:41 EDT
Deferred to 4.3 as it is not a stop ship issue for 4.2 and not a regression.
Comment 4 Dave Smith CLA 2006-10-20 18:22:49 EDT
Cannot be contained in 4.3 - deferring to 4.4.
Comment 5 Dave Smith CLA 2007-01-17 23:36:05 EST
Added sizing.
Comment 6 Dave Smith CLA 2007-03-20 08:42:15 EDT
Cannot be contained in 4.4 - deferring to future.
Comment 7 Eric Labadie CLA 2007-09-12 15:11:39 EDT
This is required from the AC perspective.
Comment 8 Dave Smith CLA 2007-09-14 11:44:28 EDT
With the fix for https://bugs.eclipse.org/bugs/show_bug.cgi?id=132225 introduced in TPTP 4.2, the Time Format field on substituion rules can now be used to generate dateTime strings for extendedDataElement values.

Therefore, I am changing this bugzilla's scope to only updating the documentation to reflect that Time Format can be used on Extended Data Element rules.  The following files need to be updated:

org.eclipse.tptp.monitoring.doc.isv/ref/rconfilestruct.html
org.eclipse.tptp.monitoring.doc.isv/tasks/tconfigureparser.html

Targetting this to fix in TPTP 4.5 release.
Comment 9 Dave Smith CLA 2007-09-14 11:45:35 EDT
Updating sizing to reflect only the documentation change is required.
Comment 10 Alex Nan CLA 2007-10-30 19:37:19 EDT
Targetting 4.5 i2.
Comment 11 Alex Nan CLA 2007-11-05 18:50:33 EST
Targetting to 4.5 i4.
Comment 12 Alex Nan CLA 2007-12-12 00:11:46 EST
Targetting to i5, couldn't be contained in i4.
Comment 13 Alex Nan CLA 2008-01-29 18:44:54 EST
Fixed.
Comment 14 Paul Slauenwhite CLA 2009-06-30 09:55:39 EDT
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 originator of this enhancement/defect has an inactive Bugzilla account 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.
Comment 15 Paul Slauenwhite CLA 2009-06-30 09:56:14 EDT
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 the originator of this enhancement/defect has an inactive Bugzilla account 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.