Menu
▾
▴
[Sblim-commit] ecute ToDo.txt,1.9,1.10
|
From: Andreas M. <ma...@us...> - 2005-04-01 17:41:15
|
Update of /cvsroot/sblim/ecute In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv31899 Modified Files: ToDo.txt Log Message: Inserted missing ToDo's from previous CVS repository, as a result renamed old 30+31 to 37+38. Index: ToDo.txt =================================================================== RCS file: /cvsroot/sblim/ecute/ToDo.txt,v retrieving revision 1.9 retrieving revision 1.10 diff -u -d -r1.9 -r1.10 --- ToDo.txt 31 Mar 2005 16:15:00 -0000 1.9 +++ ToDo.txt 1 Apr 2005 17:41:04 -0000 1.10 @@ -1,7 +1,7 @@ -ToDo List for Ecute +ToDo List for ECUTE ------------------- -Last updated: 31-Mar-2005 AM +Last updated: 01-Apr-2005 AM 1. Problem: In Rose, there are two places where the Description qualifier for @@ -112,7 +112,7 @@ 10. Problem: Tooling does not detect duplicate properties without override. - Currently, Ecute adds an override qualifier on export for REF properties + Currently, ECUTE adds an override qualifier on export for REF properties (Validate whether this is really just for REF properties). Solution: @@ -123,7 +123,7 @@ - Provide a check that just surfaces this as a warning. - The current automatic adding of overrides on REF properties stays active. -11. Problem: There is a bug in Ecute due to a misunderstanding of the +11. Problem: There is a bug in ECUTE due to a misunderstanding of the "Override" qualifier: All the properties/methods/parameters existing with the same name in base classes are considered "override" even when the override qualifier is not defined. This is related to 10 ("Tooling does @@ -182,7 +182,7 @@ 16. Document the CMPI code generator plugin in the User's Guide. Important for Cisco. -17. Update the Developer's Guide to reflect Ecute architecture. Current +17. Update the Developer's Guide to reflect ECUTE architecture. Current document corresponds to CrmTooling 1.3 18. Rose input plugin finishes with an exception if any of the selected packages @@ -306,7 +306,13 @@ Releasing memory (this can take some time depending on the number of created objects). - b) The titles of the message log window currently change for each phase, and at the end it sits on the export. I don't think it is necessary to adapt the title dynamically to the phase executing (otherwise you would need to go to error or success at the end, to be consistent). I believe it is much simpler and without any loss of usability if the title text was just fixed, e.g. "ECUTE 2.0 - CIM MOF Import" + b) The titles of the message log window currently change for each + phase, and at the end it sits on the export. I don't think it is + necessary to adapt the title dynamically to the phase executing + (otherwise you would need to go to error or success at the end, to + be consistent). I believe it is much simpler and without any loss + of usability if the title text was just fixed, e.g. "ECUTE 2.0 - CIM + MOF Import" c) Same comment for export message log. @@ -338,27 +344,27 @@ Solution: Detect the version incompatibility and suface it as an explicit error message to the user. This should be done as a general solution by catch all types - of java.lang.error and displaying an according message before terminating eCute. + of java.lang.error and displaying an according message before terminating ECUTE. We should also create a log-file that holds all outputs for stdout and stderr as a first error indication. 26. Selection of Java environment at installation time - Problem: The fact that eCute does not work with JRE 1.4.2 requires the use of + Problem: The fact that ECUTE does not work with JRE 1.4.2 requires the use of multiple versions of java for those users that use 1.4.2 for other apps. Solution: Default would be the default environment (e.g. java.exe in the path). One way to do this is to allow specification of an environment variable that the user says would point to the JRE, test that, and then use that variable in the generated .bat files. We should investigate if it is - legally possible to ship a compatible JRE together with eCute, much like it + legally possible to ship a compatible JRE together with ECUTE, much like it is done for other IBM products. 27. IBM implementation of a COM bridge There is an IBM plugin for Eclipse for accessing COM objects. Today we do this with Jacob with the following limitations: the license does not allow - us to distribute it with Ecute. it does not work with the latest JREs + us to distribute it with ECUTE. it does not work with the latest JREs The plugin commes from Rational, therefore it should be designed with an eye on REI. The artice is in Developerworks. Here is the link: @@ -368,42 +374,100 @@ The task would be to use this COM bridge when interfacing with Rose from RSA. We should also investigate whether this COM bridge can be used in an isolated Rose environment (i.e. without RSA). - + 28. Multiplicity for Rose MOF import is set to unspecified The Rose MOF import sets the multiplicity for associations to unspecified when - the Min/Max qualifiers are not specified. + the Min/Max qualifiers are not specified. Instead it needs to set multiplicity to the default values for Min/Max as specified in the qualifier mof. 29. Improve error message for mof import - + The following (erroneous) source line: - + >> string ClassName; /7 was an override of Name - + leads to this confusing error message: - + >> Error: ws-cim-example3.mof(160): Token 256.0 not expected. - + This error message needs some improvement - -30. When the selected Rose package does not contain a main diagram during export - a Nullpointer exception occurs in RoseParser::CreateCategories: - ERROR: the following unknown error was detected: - java.lang.NullPointerException - at com.ibm.ecute.plugins.input.funcionality.RoseParser.fillCategory(RoseParser.java:211) - at com.ibm.ecute.plugins.input.funcionality.RoseParser.CreateCategories(RoseParser.java:190) - at com.ibm.ecute.plugins.input.funcionality.RoseParser.Import(RoseParser.java:151) - at com.ibm.ecute.plugins.input.RoseInputPlugin.execute(RoseInputPlugin.java:150) - at com.ibm.ecute.EntryPoint.executeInputPlugins(EntryPoint.java:636) - at com.ibm.ecute.EntryPoint.<init>(EntryPoint.java:216) - at com.ibm.ecute.EntryPoint.main(EntryPoint.java:108) +30. Show Compositions with solid diamond -31. - 35. missing (lost on developerworks) + Cisco found this when testing the Rose version, with ECUTE 2.1 alpha1. We + currently ignore the Composition qualifier, when we should use it to decide + whether the composite end of a UML aggregation should be owned or not + (solid diamond vs. hollow diamond in the class diagram). -36. The entry in the list of installed software (Win XP: Control Panel / Add or Remove Programs) - should state the version being installed. + Need to verify whether this also occurs in the RSA version. Need to update + the UML mapping section in the User's guide accordingly. + +31. Test RSA version with RDM (Rational Data Modeler) + +32. Get RSA version ready for production + + This includes at least the following work: + - Update the design documentation and the User's Guide + - Place a binary package on SBLIM + - ... more ? + + We need to discuss whether the following should also be done before we call + out "ready for production": + - Port check&repair + - Port provider generation + - Item 31 (Test with RDM) + +33. Add a check option for usage of deprecated properties, methods or (association)classes. + + There is a number of ways to define "usage".: + 1. based upon IBM_* qualifiers + 2. Defined in the classes of a package + 3. Future: Defined in classes of a profile + I tend to prefer 1. for now. + +34. Add a check&repair option for role names in associations. + + The check would detect missing override qualifiers betwen equally named reference + properties in a inheritance sequence as well as any change of role names along a + chain of reference properties connected with override qualifiers. + + The repair would assume the base class of the package selected to be fixed is + correct, and the property names in the classes in the selected package would be + adjusted if needed, and a missing override would be created, and one that changes + the name would be also adjusted. + +35. ECUTE fails on MOF export if error in another package + + When exporting package A, and there is an error in a package B, then even if B is + not used by A in any way, ECUTE failt to export package A. + This should be changed to only have errors that affect the export of A, cause + the export to fail. + + Other operations (e.g. provider generation) should be tested whether they also + need to be changed accordingly. + +36. ECUTE does more checking when exporting MOF than when checking. + + Some CbC models exhibited that behaviour. Need to dig out from CbC CVS and test, + to understand the cases. Probably a version around 2/2005. + +37. (Was 30.) When the selected Rose package does not contain a main diagram + during export a Nullpointer exception occurs in + RoseParser::CreateCategories: + + ERROR: the following unknown error was detected: + java.lang.NullPointerException + at com.ibm.ecute.plugins.input.funcionality.RoseParser.fillCategory(RoseParser.java:211) + at com.ibm.ecute.plugins.input.funcionality.RoseParser.CreateCategories(RoseParser.java:190) + at com.ibm.ecute.plugins.input.funcionality.RoseParser.Import(RoseParser.java:151) + at com.ibm.ecute.plugins.input.RoseInputPlugin.execute(RoseInputPlugin.java:150) + at com.ibm.ecute.EntryPoint.executeInputPlugins(EntryPoint.java:636) + at com.ibm.ecute.EntryPoint.<init>(EntryPoint.java:216) + at com.ibm.ecute.EntryPoint.main(EntryPoint.java:108) + +38. (was 36.) The entry in the list of installed software (Win XP: Control + Panel / Add or Remove Programs) should state the version being installed. |
