Issue 5938: What has happened to all of the older OTS issues (ots-rtf) Source: Red Hat (Dr. Mark Little, mlittle(at)redhat.com) Nature: Clarification Severity: Significant Summary: What has happened to all of the older OTS issues that used to be on http://www.omg.org/issues/transactions.html ? If you go to that old link you'll find them still, but they do not carry across to the new web page. They indicate that they haven't been addressed, when I know that many of them were. The worrying thing is that some of the issues that were voted on and accepted (e.g., 1317) seem not to have made it into the latest spec. after 5 years. Are there others? Unfortunately the mail archive seems to only go back to 1998, when I know it should go beyond that. BTW, the issue with 1317 was that the current field in the PropagationContext can't legally be called current since fields/interfaces aren't allowed to differ by case. So the suggestion (and vote) was to change it to currentTransaction. The latest spec. still has current in it though. Resolution: Revised Text: Actions taken: May 15, 2003: received issue Discussion: End of Annotations:===== From: webmaster@omg.org Date: 14 May 2003 06:48:51 -0400 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Mark Little Company: University of Newcastle upon Tyne mailFrom: m.c.little@ncl.ac.uk Notification: Yes Specification: Object Transaction Service Section: all FormalNumber: 01-05-02 Version: 1.2 RevisionDate: May 2001 Page: all Nature: Clarification Severity: Significant HTTP User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) Description What has happened to all of the older OTS issues that used to be on http://www.omg.org/issues/transactions.html ? If you go to that old link you'll find them still, but they do not carry across to the new web page. They indicate that they haven't been addressed, when I know that many of them were. The worrying thing is that some of the issues that were voted on and accepted (e.g., 1317) seem not to have made it into the latest spec. after 5 years. Are there others? Unfortunately the mail archive seems to only go back to 1998, when I know it should go beyond that. BTW, the issue with 1317 was that the current field in the PropagationContext can't legally be called current since fields/interfaces aren't allowed to differ by case. So the suggestion (and vote) was to change it to currentTransaction. The latest spec. still has current in it though. Mark.