Upgrading to a Maintenance Release
OptimalJ maintenance releases (such as service packs or releases with version number of the pattern #.#.0#) provide updates to generated code and the patterns applied to models. For more information, see the below table.
To take advantage of these changes, you must follow this procedure for each OptimalJ project when upgrading to the maintenance release:
Version Control Systems
The MCR files used to map generated files to model elements are not stored in version control systems. These MCR files are required when upgrading to a maintenance release. Before upgrading to a maintenance release, you must restore these files by completing steps 1 and 2 in the old version of OptimalJ (Updating all models ensures that all models are synchronized, while generating code creates the MCR files). Then install the maintenance release and follow the procedure described above.
| Bug number | Severity | Summary | Reported version | Fix version | Description | Release notes |
|---|---|---|---|---|---|---|
| 30308 | 1-Critical | Cannot edit type of WebComponentAttribute in Professional Edition built on Eclipse | 4.1.ITB1 | 4.1.00_SP1 | Not possible to edit type of WebComponentAttribute with property editor. |
Fixed the implementation in the model of WebComponentAttribute. |
| 30040 | 2-Major | Cannot start Business Expression Server on OptimalJ PE built on Eclipse | 4.1.ITB1 | 4.1.00_SP1 | Start fails with the dialog "Expression Library not found: dbe_library.xml". |
issue fixed by improving startup order. |
| 30046 | 2-Major | Problems editor does not show problem description when opening a problem | 4.1.ITB1 | 4.1.00_SP1 | When opening the problem editor from the problems view, the error would not be shown initially in the problems part. |
Fix opening the problem editor from the problem view |
| 30052 | 2-Major | Module dependencies missing for subsystem 4th using indirectly subsystem 2nd. | 4.1.ITB1 | 4.1.00_SP1 | For application with 3 subsystems: a,b and c - each with one domain class, like: ClassA (0..1) --- (0..n) ClassB (1..n) ---- (0..1) ClassC where: ClassA and ClassB are published subsystems ClassC is using subsystem, and uses subsystems "a" and "b" After action -Generate All Models for using subsystem(c) in EJBModule for subsystem "c" there is a missing module reference to used subsystem "a" application module. The workaround is to add this module to EJBModule. ->a.application.business.common.aApplication if this module is not specify there will be compilation error in ClassCSvcBean.java ->dstUpdateObject.setClassAClassA(srcUpdateObject.getClassAClassA()); NOTE: this action is not required in OptimalJ NB |
Fixed |
| 30070 | 2-Major | Migration: 'usedModule' no set when using a type from a dependant subsystem in Professional Edition built on Eclipse | 4.1.ITB1 | 4.1.00_SP1 | In Professional Edition built on Eclipse, one can create subsystems A and B (depending on A). If B uses _only_ a type from A than the EJB module of B does not have the 'usedModule' set to point to the applicationModule of A. As a result, a compile error can be observed. |
The issue was caused by a classpath problem, and has been fixed. |
| 30071 | 2-Major | Migration: application export fails to package Java signatures | 4.0.00_SP4 | 4.1.00_SP1 | Backup: instead of waiting for the migration scripts to create backups, the MainMigrator now creates a zip containing all file and directory entries prior to migration. This solves two bugs: 1) metamodels were not backed up and 2) the migration tool would overwrite it's own backup with an application export backup. Migration: All application exports are now extracted prior to migration. All entries are then mounted together and migrated. This fixes migration of any model that depends on an application export. |
|
| 30092 | 2-Major | Using Container Managed Relationships for mandatory many-to-many associations can cause problems (JBoss). | 4.1.ITB1 | 4.1.00_SP1 | When using mandatory ComponentReferences between EJBEntityComponents, OptimalJ defaults to using Bean Managed relationship management. If you override this setting and choose Container Managed, CMR, (which some application servers, including JBoss, support), you might run into a problem. The problem occurs when you have an EntityComponent with multiple CMR/mandatory component references, one of which is part of a many-to-many association. The default configuration used for an association is "Standard CMP 2.x EntityBean" (XxxEjb-jboss.xml). For CMR/mandatory we use the "INSERT after ejbPostCreate Container" configuration. An exception is mandatory many-to-manies. If you have multiple EJBEntityComponentReferences for one component, one of which is such a mandatory many-to-many, OptimalJ will (depending on the relative position of reference in the repository) use "Standard CMP 2.x EntityBean" for ALL references of that component. This is incorrect. The problem is not so much with the mandatory many-to-many references (for which both configurations are acceptable), but with the other mandatory references of that same component. |
Fixed in OptimalJ version 4.2. The presence of a mandatory many-to-many no longer effects the other references. An effect of this fix is that now the "INSERT after ejbPostCreate Container" configuration is used for all mandatory references (including many-to-many). |
| 30094 | 2-Major | WEBComponent wizard offers and selects QueryDataSchema from outside the WEBModule causing dependency problems. | 4.1.ITB1 | 4.1.00_SP1 | WEBComponent wizard searchs for all suitable QueryDataSchemas in the model and offers one to the user as possible class. When there is more than one WEBModule in the application, a dependent module can have similar WEBDataSchema. If this is selected, the WEBModule of WEBComponent gets a dependency on the already dependendent WEBModule causing syclic dependency. |
1) The initial selection should use the 'nearest' Query WEBDacaClass. Under normal conditions that will be ok. 2) The wizard no longer allows Query WEBDataClasses from a wrong Module. Wrong is: not from the same Module as the WebComponent or a Module that a usedModule of the Components Module. |
| 30124 | 2-Major | Generated IP ModelDoc,MyJSP, MyTP sample plugins for Eclipse give Errors when I generate code for CRM application. | 4.1.ITB1 | 4.1.00_SP1 | corrected dependencies in plugin xml file | |
| 30128 | 2-Major | ClassNotFoundException when starting Eclipse with IP MyTP plugin generated from OptimalJ AE. | 4.1.ITB1 | 4.1.00_SP1 | corrected dependencies in plugin xml file | |
| 30151 | 2-Major | Re-Deploy in UID of PEE does not redeploy war file: shows Archive File Selector with only ejb jar file | 4.1.ITB1 | 4.1.00_SP1 | In PE built on Eclipse UI Designer the re-deploy option does not work. It does always show a dialog 'Archive File Selector' with a list of files, which only contains ejb jar file . The war file is not listed ! After pressing OK in this dialog only the ejb jar file is redeployed and not the war file. This implies that the changes in the web component or web pages are not shown and that the start page is not opened again in your browser. It is a PE built on Eclipse specific issue, because in PE (Netbeans) it works fine. |
The "Start Application Server" started while the "Generate Archives" action was still busy. Fix: make "Generate Archives" a blocking action. This has as additional effect that the progress window during "Generate All Archives" waits until the ant- scripts have finished running. |
| 30169 | 2-Major | Associations are deleted when deleting shortcuts to associations | 4.1.ITB1 | 4.1.00_SP1 | fixed | |
| 30264 | 2-Major | 'Using the Web User Interface Designer' tutorial should add serving attribute | 4.1.ITB1 | 4.1.00_SP1 | The tutorial 'Using the Web User Interface Designer' should describe to add a serving attribute 'serviceagreement' in step 5.4. |
Fixed |
| 30311 | 2-Major | DataObject does not generate operation for DataClassOperation | 4.1.ITB1 | 4.1.00_SP1 | Steps to Reproduce: *Create a Domain Class with a DomainOperation and set category to DataLevel *Udpate all models Notice that the application common for that data class contains the operation *Generate all code *Open the DataObject Observed behaviour: There is no method which corresponds to the operation corresponding to the dataclass Expected behaviour: That the operation should be available in the data object |
Fixed |
| 30384 | 2-Major | PDF documentation is incomplete | 4.1.ITB1 | 4.1.00_SP1 | Some tutorials are missing from the PDFs, and the Eclipse Tutorials PDF contains some content specific to the NetBeans editions. |
The PDFs are corrected. |
| 28898 | 3-Normal | Session component wizard does not allow references to stateless DACs | 4.0.00 | 4.1.00_SP1 | When creating a session component that retrieves data from a DAC, OJ forces the user to make the session bean stateful in the edit wizard. If the session bean does not use the page iterator there is no reason why it should have to be stateful because a new instance of the DAC is obtained each time it is being called. |
Enhanced the SessionBean wizard. Added a model warning that a stateless sessionbean using DAC's that support PageIterator will not result in a working PageIterator. |
| 29728 | 3-Normal | Webdatareference of querydataschema is not set reliably by copier | 4.0.00_SP3 | 4.1.00_SP1 | Update all models sometimes has the effect that the "queryResult" webdatareference is updated to a wrong data class. The QueryDataSchema reference gets it's type from WEBComponent in a settings object. This object is not persisted and when updating all models, this information is not found. A resolve to find a suitable DataClass may sometimes return a different dataclass than intended. |
Now during an Update model the existing value of the type attribute of WEBDataReference is not changed and if no value is set or the existing value is not valid, a Warning is given in output. |
| 29736 | 3-Normal | Transactions are left open if store fails with exception | 4.0.00_SP6 | 4.1.00_SP1 | Transactions are left open if store fails with exception (it only happens if the business facade has got local transaction management). |
In BusinessFacade.doStore() we are now catching all RuntimeExceptions, rollback the transaction, and rethrow the RuntimeException. |
| 29740 | 3-Normal | Incorrect sort order when retrieving data objects from DACs | 4.0.00_SP6 | 4.1.00_SP1 | When retrieving a collection of DataObjects, the DAC iterates the Key Collection and builds up a single SQL query with a where clause containing all keys with "OR" between. The database will deliver the result set in arbitrary sort order, thus disregarding the initial sort order defined in the initial query for primary keys. |
Fixed, the DAC Component re-orders the resulting DataObject collection to reflect the supplied KeyClass order |
| 29788 | 3-Normal | Missing key for AlturaPreConditionException | 4.0.00_SP6 | 4.1.00_SP1 | Missing key for AlturaPreConditionException and AlturaPostConditionException in AlturaResources.properties. |
alturalib.application bundle.properties file has been updated with two labels: ERR_PreConditionException=Pre-condition failed: {0} ERR_PostConditionException=Post-condition failed: {0} |
| 29806 | 3-Normal | [GeneratorBase] and [NamedBlockText] messages in ide.log with generate code | 4.0.00_SP6 | 4.1.00_SP1 | During generate code of 2 interdependent applications using subsystems a lot of debug messages are displayed the DOS box and ide.log about [GeneratorBase] and [NamedBlockText]. |
Messages suppressed. |
| 29808 | 3-Normal | struts attribute styleClass generated in non struts html element | 4.0.00_SP6 | 4.1.00_SP1 | If you add a new WebTextField which is ***not mapped to anything***, the input statement has a attribute styleClass instead of class defined. |
For plain html elements the class attribute is used. |
| 29824 | 3-Normal | Editing a stored record fails when primary key contains enumeration from another package (part 2) | 4.1.ITB1 | 4.1.00_SP1 | Storing fails for a model in which the primary key contains enumeration from another package. |
1. Removed the duplicate editbox from the page. 2. Corrected the build key methods (3) to use the correct parsing routines. |
| 29838 | 3-Normal | an xsd element refering to a schema is not supported | 4.1.ITB1 | 4.1.00_SP1 | A wsdl containing an xsd:element referencing an xsd:schema is not imported correctly into OJ; the reference on the xsd:element becomes null. |
xsd:element referencing a schema is supported. I.e. also by web service TP and IPs. |
| 29967 | 3-Normal | The OJFND024 modelcheck should ignore WSSigningProperties and WSVerifyingProperties | 4.0.00_SP6 | 4.1.00_SP1 | During the model check, there is a warning "WSSigningProperties can't be connected to a module". It is not possible to select a module because the signer-object doesn't accept any module. |
The OJFND024 modelcheck ignores WSSigningProperties and WSVerifyingProperties. |
| 29971 | 3-Normal | MySQL: drop relationship statements are incorrect. | 4.1.ITB1 | 4.1.00_SP1 | The generated relationships scripts hold incorrect statements. Execution results in MySQL errors. |
Fixed |
| 30067 | 3-Normal | Fault in the actionmapper pattern of the UpdateAction java module | 4.0.00_SP6 | 4.1.00_SP1 | Enabling UI designer for a given WEB component (MasterClassSvc) seems to edit the generated code in mapped java file (MasterClassSvcUpdateAction.java). Clicking edit button results in a null page because of mappings in actionMapper method. |
The code generated for the actionMapper methods was wrong. Only when it's determined that the button is pressed, the key information needs to be gathered and the application needs to forward to the actionMapping found. This is now implemented. |
| 30075 | 3-Normal | WebOperationParameter with styletype causes compile error. | 4.0.00_SP6 | 4.1.00_SP1 | StyleType is never supported for WebOperationParameters. | Implemented modelcheck to warn customers. |
| 30145 | 3-Normal | valign="center" should be valign="middle" according to the HTML 4 spec | 4.0.00_SP6 | 4.1.00_SP1 | In generated HTML pages for JSPs the value for the valign property is "center". This should be valign="middle" according to the HTML 4 spec Observed behaviour: |
|
| 30182 | 3-Normal | Making a DAC read-only results in an error in the WebFromClassPattern when updating all models | 3.3.01 SP2 | 4.1.00_SP1 | If the DAC of a class that has a subclass is made read only then update all models fails in the WebFromClassPattern. In earlier versions of OptimalJ an exception in the request processor also occurs. |
Fixed |
| 30228 | 3-Normal | 'filterHtml' property of WebOutput type element does not work as expected | 4.0.00_SP6 | 4.1.00_SP1 | Using the 'filterHtml' property of WebOutput type elements, user should be able to set the filter to be 'true' or 'false', however, it does not seem to work this way. |
Introduced a property 'filter' for some widget elements, at least for WebLabel. Default is true. The Initial Layout wizard/copier sets the filter property according to the WebOutputType.htmlFilter setting. The code generator for WebLabel generates code accordingly. |
| 30309 | 3-Normal | EnumType lost data while widget changed to webLabel | 4.0.00_SP6 | 4.1.00_SP1 | Fixed in the saveBean method. | |
| 30318 | 3-Normal | Buttons with an X Coordinate > #Columns don't get displayed | 4.1.ITB1 | 4.1.00_SP1 | Sometimes the generated WebPage that gets generated by the initial layout wizard gives X Coordinates that are not right. In the canvas the buttons are visible, but at runtime the buttons are not visible. This is because the button(s) have an X Coordinate greater than the number of Columns. |
Fixed by adding a modelcheck to warn you of the wrong coordinate. |
| 30319 | 3-Normal | new modelcheck documentation needed for parameters with styletype | 4.1.00_SP1 | 4.1.00_SP1 | New modelcheck warning WEB918 introduced. | The warning has been documented |
| 30324 | 3-Normal | Exceptions in DAC are printed to standard output | 4.0.00 | 4.1.00_SP1 | Exceptions that are caught in the DAC are printed to standard output instead of logged using the logger. |
Fixed |
| 30325 | 3-Normal | New modelcheck for WebWidget with X coordinate that is out of bounds | 4.1.00_SP1 | 4.1.00_SP1 | New modelcheck warning WEB096 has been introduced. | Warning has been documented. |
| 30361 | 3-Normal | Code generated for read-only DAC does not compile when class has subclass which is not readonly | 4.1.00_SP1 | 4.1.00_SP1 | Modelcheck has been added to warn for this situation. | |
| 29488 | 4-Minor | Unclear selection of Query WebDataClass in wizard | 4.1.ITB1 | 4.1.00_SP1 | - the dropdownbox will contain all valid queryWebDataClasses for the current Served Attribute and Served dataclass. - the dropdownbox will also contain the <not set> - the tooltip of the dropdownbox will show the full qualified names of the classes. - the browsebutton will pop up the same tree with only valid query classes. The current selection of the drowdownbox will be the initial selection of the tree. |
|
| 29928 | 4-Minor | WebAction of type None do not get a default success event on creation. | 4.1.ITB1 | 4.1.00_SP1 | Create a new WebAction of type none. The WebEvent panel does not contain any default event (e.g. success which is used as fallback in generated code). |
Created an initial sucess event for NONE type actions, allow editing the name and deleting, but do not accept an empty event list. Additional: created a model-check to ensure that a WebAction has the proper number of events (depending on the type of action). This is a Warning as the action will be useless, but not harmfull. |
| 29310 | 2-Major | EJB-QL compilation under Eclipse fails for J2SDK 1.4.2_06 | 4.1.ITB1 | 4.1.00_SP2 | When you try to use the EJB-QL compiler with JDK1.4.x then some classes that are included in the JDK1.5 cannot be found. You will have an expectation similar to: ... [java] compileEJBQL: [java] [EJBQLSyntaxCheck] java.lang.NoClassDefFoundError: org/w3c/dom/ranges/DocumentRange ... |
|
| 30033 | 2-Major | Generate Code results in exception when Code project is closed | 4.1.ITB1 | 4.1.00_SP2 | Typical scenario where this might be happening: A user is focussed on the business logic, closes the web project (otherwise it will be build very often without benefitting the user). Now he generates all code and he is faced with a generic exception. |
Fixed by warning the user to open his code-projects prior to generating code. |
| 30262 | 2-Major | update general procedure in help topic Migration Process | 4.1.ITB1 | 4.1.00_SP2 | The documentation on migration from OptimalJ 4.0 to 4.1 is not sufficiently clear, particularly for users of Eclipse-based editions. The documentation should make clear that the migration tool creates an application export file, which can then be imported into OptimalJ 4.2. |
The migration instructions have been updated. |
| 30267 | 2-Major | Store not invoked | 4.1.ITB1 | 4.1.00_SP2 | If you deploy a user-defined webcomponent for a class that has a mandatory association but do not define the associated class as serving attribute, then store will not be invoked when pressing 'store' |
The error is tagged with a property which has the value which is equal to the DataClass name. The WebErrorPanel in the jsp page is tuned to show only those errors that are tagged as GLOBAL. WebErrorLabels will show errors that are specific to attributes, the rest of the errors should be shown in the global WebErrorPanel. * Change to the product: Made sure the mandatoryness constraint violations as global errors |
| 30310 | 2-Major | Code for DAC component gives compile error in guarded block | 4.1.ITB1 | 4.1.00_SP2 | DAC component for class with relationships generates code that does not compile if the related classes do not have a DAC component generated for them |
The fix makes the finders work again without the ComponentReferences |
| 30335 | 2-Major | Migrated domain execptions do not properly display names in xenon diagrams | 4.1.ITB1 | 4.1.00_SP2 | Adapted the OptimalJ 4.0 to 4.1 migration script for xenon diagrams. |
|
| 30354 | 2-Major | GridAction on Dummy Web Data Class gives compilation error | 4.1.ITB1 | 4.1.00_SP2 | Binding an action of type Grid to a dummy WebDataClass causes a compilation error when down references are defined on the dummy WebDataClass |
Fixed |
| 30406 | 2-Major | Missing code in the ejb tier - unable to edit related class in generalization | 4.0.00_SP6 | 4.1.00_SP2 | Unable to edit data from teh sub class for a class that's related to the parent class. |
In ServingAttribute.tpl generated code for method initObjectCache() is changed so that it sets the retrieve/update collections also for the supertypes. A block of code is moved to a new template MAPINIT. This block of code remained the same, except that the call SCHEMAWALKER(component, CACHEMAP, null,null, null, hash) has been replaced by the call SCHEMAWALKER(servedType, CACHEMAP, hash). |
| 30427 | 2-Major | Web compile error after migrating an application with inheritance and service byValue re-used | 4.1.00_SP2 | 4.1.00_SP2 | The TPL didn't use the extendedFeatures, hence the inherited reference didn't get processed. |
|
| 30470 | 2-Major | Executing Creating TP tutorial results in Build Failed | 4.1.ITB1 | 4.1.00_SP2 | The "Creating Technology Patterns" tutorial cannot be completed because it specifies an incorrect module ID in Step 8. |
The tutorial is updated with the correct module ID. |
| 30473 | 2-Major | Custom codes written in the client-config.wsdd are lost every time you generate codes. | 4.1.ITB1 | 4.1.00_SP2 | Custom code entered in the free blocks in client-config.wsdd are overwritten with the original generated code when code is re-generated. |
|
| 30513 | 2-Major | Context item changed when invoking an isolated webflow of another component | 4.1.ITB1 | 4.1.00_SP2 | ComponentState property for WebInvocationNode 'Isolate' can indicate that the ContextStack for calling WEBComponent should be isolated from the Called WEBComponent. However, a reference to this Stack remained in the session attribute and the called WebFlow in other WEBComponents could (accidentally) modify the contents of the Stack. |
|
| 30571 | 2-Major | foreign keys as primary unique constraint results in generated code that use deprecated dataobject methods | 4.1.ITB1 | 4.1.00_SP2 | Warnings are given in SessionBean class about using deprecated DataObject methods. |
Calls to the deprecated methods in SessionBean class are replaced with calls to the new methods. |
| 21155 | 3-Normal | Cannot create AlturaComment in application modules. | 3.3.Phase1 | 4.1.00_SP2 | It is not possible to create an AlturaComment and attach it to a module in the application model. |
|
| 27295 | 3-Normal | ClearCase: Using only ClearCase should not require .stignore file in home directory | 4.0.00 | 4.1.00_SP2 | Working with versioned controlled file system in ClearCase requires .stignore file - Even when .ccignore file (required for ClearCase) is present in home directory, it keeps reporting about missing .stignore file. This should NOT be the case because .stignore file is only required for StarTeam, and not for ClearCase! |
|
| 30200 | 3-Normal | WebComponentFromWebServicesPattern has module <not set> | 4.1.00_SP1 | 4.1.00_SP2 | After importing a web services WSDL or XML file, checking the web service model results in a warning OJFND024 - WebComponentFromWebServicePattern is not a part of a module. |
|
| 30231 | 3-Normal | It should not be possible to select a service schema dataclass in the DAC wizard | 4.0.00_SP6 | 4.1.00_SP2 | It is possible to create a DAC on a service model schema. No model warning/error is given during the model check phase. During code generation an error is generated. |
Changed the wizard for DAC so that it doesn't allow selecting a DataClass that is generated from a service model Created a model checker for a case when the ServingAttribute type is set to a service model DataClass manually via the properties file |
| 30237 | 3-Normal | ClearCase: Web JARS are always Checked out by default on TreeFS mounts | 4.0.00_SP6 | 4.1.00_SP2 | The alturalibDelpoyWeb.jar, alturalibDeployWebBOM.jar and struts12.jar are always checked out by default (without having been changed). |
Clearcase actions on jarfiles in TreeFS have been disabled. The vcs-import functionality still imports the files correctly into the ClearCase repository. If you have any need to change those files, or add additional jarfiles to ClearCase, you should execute version control commands on these files outside of OptimalJ (when OptimalJ is not running). |
| 30332 | 3-Normal | UML import from rose can't handle aggregation=aggregate | 4.1.ITB1 | 4.1.00_SP2 | In Rational Rose 2002 a shared aggregation is indicated using XMI syntax 'aggregate', while in OJ it is indicated using XMI syntax 'shared'. The cause of the symptom is that during UML import no conversion is done between these syntaxes, while such a conversion should be done. |
Conversion has been added |
| 30399 | 3-Normal | UML export to Rose 2002 doesn't export shared aggregation as 'aggregate' | 4.1.ITB1 | 4.1.00_SP2 | In Rational Rose 2002 a shared aggregation is indicated using XMI syntax 'aggregate', while in OJ it is indicated using XMI syntax 'shared'. The cause of the symptom is that during UML import no conversion is done between these syntaxes, while such a conversion should be done. |
Fixed |
| 30400 | 3-Normal | When export to Rose2002 UML, wrong xml header written, so that wrong xsl script (being OJtoOJ.xsl) is used during import | 4.1.ITB1 | 4.1.00_SP2 | When you export to UML (selecting Rational Rose 2002 / 2003), OJ uses the UMLtoRR2002.xsl script, but the header in the export file doesn't denote that it is for RR2002. That causes that when you later import the exported file into OJ (thus if you do a short round trip), it uses the OJtoOJ.xsl script, while it should use the RR2002toUML.xsl script. |
Changed the UMLtoRR2002.xsl file and set: XMI.exporter to "Unisys.JCR.2" XMI.exporterVersion to "1.3.6" |
| 30417 | 3-Normal | Eclipse model-merge logging information in documentation | 4.1.ITB1 | 4.1.00_SP2 | OptimalJ built on Eclipse allows model merge actions to be logged. The log, however, is not generated by default, and documentation is required that describes how to generate the log by changing the configuration settings. |
Updated documentation for OptimalJ built on Eclipse with details of how to log model merge actions. |
| 30430 | 3-Normal | Doc: incomplete information for converting patterns from NetBeans to Eclipse | 4.1.ITB1 | 4.1.00_SP2 | The documentation lacks a topic describing how to convert NetBeans modules built with the Architecture Edition into Eclipse plugins. |
A topic has been added, and is linked to from the Architecture Edition "What's New" topic in the online help. The new topic is called "Converting Metamodels and Patterns to Eclipse Plugins". |
| 30848 | 1-Critical | Q-MD jsp page causes servletException when deploying on webSphere. | 4.1.ITB1 | 4.1.00_SP3 | he user defined Q-MD web component will fail when accessing because the jsp gets the following exception. ServletException in '/optishopWeb/MyCustomerMainPageContent.jsp': /optishopWeb/MyCustomerMainPage Content.jsp(230,56) Attribute queryResult[ has no value And the line 279 is : <altura:errors property="<%= "queryResult[" + (PanelTestQueries1_PanelQueryResult_QueryResultReferencePa nel_GridRowPanel_r owNumber - 1) + "].customerId" %>"/> |
Quotation handled correctly. |
| 30573 | 2-Major | altura runtime exeption when selecting an up reference that is part of the primary key | 4.1.ITB1 | 4.1.00_SP3 | Bug was caused by changed key behaviour in data objects. The old implementation allowed for inconsistency between its key field and its other (key_nretrieved) fields. Particulary after a setKey(...), the key_unretrieved fields are not changed to reflect the new key. This behaviour, however, was necessesary for this particular model. So we changed setKey to mimic this behaviour. |
|
| 30687 | 2-Major | Follow up from bug 30513 - WebInvocationNode option 'Isolate' does not work across subsystems | 4.1.ITB1 | 4.1.00_SP3 | For WebInvocatioNode an option(property) is introduced in 4.1 to isolate the ComponentState when going to another WebFlow. However, when going to another subsystem, the returning node is not found by the WebServer. This is becasue the contextRelative property of the return actionForward is overwritten in AlturaLeaveFlow action when adding the dispatch parameter. |
Fixed by a change in the alturaLibDeployWeb.jar. OptimalJ will automatically detect and update the outdated jarfile in your project after installation of this service pack, when you newly generate code. |
| 30688 | 2-Major | Modifications to UI Designer tutorial and additional tasks regarding use of UI Designer needed | 4.1.ITB1 | 4.1.00_SP3 | Documented | |
| 30751 | 2-Major | Adding extra JavaScript to all the WebPages | unspecified | 4.1.00_SP3 | The following joinpoints have been added: /* Joinpoint for JavaScript includes */ JSINCLUDES(WEBComponent,WebPage /* == null in case of a WebTemplate */) /* Joinpoint for additional code in initPage */ JPINITPAGE(WebPage) /* Joinpoint for additional code in init<WebTemplate.name> */ JPINITTEMPLATE(WebTemplate) /* Joinpoint to add additional JavaScript within the <script> tag of the WebPage */ JPJAVASCRIPT(WebPage) |
|
| 30815 | 2-Major | Business methods invoked as finders by UI Designer | unspecified | 4.1.00_SP3 | A user wants to retrieve data from an EIS (an IMS database, for example) in a Session Bean or a Business Logic Component and map the retrieved data to an ApplicationDataClass DataObjects. The session bean/BLOC method that retrieves data from the EIS and presents it in the form of DataObjects must: 1. Be recognized by OJ as a query method so that a business facade component that corresponds to the session bean or a BLOC can correctly handle and cache DataObjects retrieved; 2. Be implemented as a free block so that user can insert necessary JCA logic to access the EIS and convert retrieved data into DataObjects. |
Fixed in 4.1.00_SP3. The algorithm is changed so that business methods of a session bean or a BLOC that meet the following alternative set of criteria are also recognized as query methods: 1. The return type of the business method is the same as that of session bean's serving attribute; and 2. The business method contains a Tag repository object with the name "query". For the Presentation Tier, if user wants to use this Query Operation as part of a RetrieveAction and QueryDataSchema, the multiplicity of the returnParameter must be set to 'zero or more'. |
| 30889 | 2-Major | Generating EJB code fails when domain classes are in different subsystem | 4.1.ITB1 | 4.1.00_SP3 | When dbms module is in a different subsystem from the common module, a RuntimeException is thrown on ejb/dao code generation: Error in template com.compuware.alturadev.ejb.ipatternEJB20.EJBENTITYCOMPON E NTGENERATOR: Either there is a problem in your model that the model check did not catch, or there is a problem in your implementation pattern : submit a bugreport (with ide.log) to your pattern provider. |
Fixed in 4.1.00_SP3. The algorithm for finding the dbms module is changed to be independent of the subsystems, so code generation continues. |
| 30471 | 3-Normal | OptimalJ/OptimalView documentation incorrect | 4.1.EC | 4.1.00_SP3 | The section "Create the SalesOrder WebPage" contains a few issues, which is confusing. |
Documentation has been improved in this area. |
| 30597 | 3-Normal | Custom pattern doesn't compile for eclipse. | 4.1.ITB1 | 4.1.00_SP3 | When creating patterns for deployment to eclipse PE, generating code or build scripts does not update eclipse pluginPath.property file, causing the build for the PE eclipse platform to fail with compiler errors. |
Since the PluginPath.properties setting is generated in a free block, the value does not get updated on regeneration. Change to the product: PluginPath.properties is empty when generating code without the eclipse setting set. When executing the build script for Eclipse, the build will fail when the right properties are not available. |
| 30619 | 3-Normal | Incorrect deployment descriptor generated when parameter of type collection used | 4.1.ITB1 | 4.1.00_SP3 | When defining an EJB method parameter with multiplicity of zero or more (collection), the class name generated in the <method-param> tag of the ejb-jar deployment descriptor contains a duplicate package definition. |
Correct fully qualified class name is generated |
| 30622 | 3-Normal | UsedServingAttribute gets lost when creating new operation and delegating it to an operation of DAC. | 4.0.00_SP6 | 4.1.00_SP3 | If the check-box "Manage Reference to Data Access Component" is off in the EJBSessionComponent wizard, DAOServingAttributes are always cleared from the usedServingAttribute list when editing the wizard. |
Problem is fixed. "Manage Reference to Data Access Component" in the EJBSessionComponent wizard is always checked-on when there is a DAOServingAttribute in the usedServingAttributes list. |
| 30623 | 3-Normal | NPE in webflow layouter | 4.1.ITB1 | 4.1.00_SP3 | A reasonably large WebFlow containing 15-20 nodes or a slower machine may cause this problem easily. The problem is that the layout calculation has a fixed time allotted. And the time can be over without the layouter providing any result if the processor is slow or is doing something else in parallel. |
NPE checked |
| 30656 | 3-Normal | Space in panel name should not be allowed | 4.0.00_SP6 | 4.1.00_SP3 | Space in panel name should not be allowed. There is no warning thrown if the panel contains spaces, however, there's an error upon runtime. Steps to Reproduce: - Create a web component and a page. Include a space in the panel name. - Generate all code, compile and test the application. Note the error. |
To prevent spaces in panels a name regulator in the model has been added. |
| 30662 | 3-Normal | Database Seq Gen for DomainUniqueConstraints | 4.1.00_SP1 | 4.1.00_SP3 | When using MSSQL Server 2000, OptimalJ is generating database sequences for both the primary key and the DomainUniqueConstraint at the DBMS level. The domain unique constraint is not reflecting the use of database sequences at the code level though. |
Sql create script has been corrected to generate IDENTITY column only for primary keys when using MSSQL Server 2000. |
| 30701 | 3-Normal | Formatting not applied to webdataattributes consistently | 4.1.ITB1 | 4.1.00_SP3 | Template com.compuware.alturadev.web.ipattern.userdef.action.FORMF ROMPARAMETERS handles all kinds of datatypes, but is not taking notice of WebOutputTypes. |
Template now aware of WebOutput types |
| 30833 | 3-Normal | Two initial upper case letters in many cause compile problem in gridaction | 4.1.00_SP2 | 4.1.00_SP3 | Fixed | |
| 30836 | 3-Normal | Incorrect SQL created for Finder methods for DACs when multiple associations exist between same classes | 4.1.00_SP2 | 4.1.00_SP3 | OJ generates wrong SQL statement and SQL parameters for manually created finder methods for DAC, when multiple associations exist between same classes. |
Fixed in GenerateDefaultWhereClause.tpl |
| 30843 | 3-Normal | SQL reserved words lead to compilation problems | 4.1.00_SP1 | 4.1.00_SP3 | Importing a database table with name beeing an ansi 92 sql reserved keyword, leads to compilation errors in the generated code. |
Changed the DAO templates to replace the quotes in the code. |
| 30846 | 3-Normal | Methods generated twice in the code. | 4.1.00_SP2 | 4.1.00_SP3 | Compile error in session bean class: 'retrieveCollectionXInsideX is already defined'. |
Fixed by changing the name of the method to include the class name and the reference name. This bug unfortunately introduced an migration issue in the 4.1sp3 and upwards: INCOMPATIBILITY: The generated method names for references have changed from "Inside" UCF(refToInner.name) to "Inside" UCF(refToInner.owner.name) UCF(refToInner.name) Examples: For DataClass A which has DataReference x to DataClass Z: retrieveCollectionZInsideX has been renamed to retrieveCollectionZInsideAX,. convertZInsideX has been renamed to convertZInsideAX retrieveZInsideX has been renamed to retrieveZInsideAX MIGRATION SOLUTION: Regenerate all code and adpat all call to incolved methods. USER's SOLUTION: If calls are made to such reference-related from free blocks, adapt the method names in those calls |
| 30910 | 3-Normal | Formbean not generated in specific situations | 4.1.00_SP2 | 4.1.00_SP3 | Calculation of component forms does not correctly calculate required forms for inherited classes. |
TPL change in com.compuware.alturadev.web.ipattern.lib.traversal.ALLUSED WEBCLASSES to letWEBTangibles used in a component also consider inheritance hierarchies. = For all WebTangibles (e.g. WebPages, WebActions) that use a non-served WebDataClass now also inheritance is taken into account. |
| 30957 | 3-Normal | Compile error when using candidate value in Web Dataclass | 4.1.00_SP2 | 4.1.00_SP3 | ompile error when using candidate value in Web Dataclass used by a WebComponent's New Action. |
Generate the correct call in the new action. |
| 30764 | 4-Minor | Traceability documentation incomplete for WebOutputTypes of DecimalFormat | 4.1.00_SP1 | 4.1.00_SP3 | Fixed | |
| 30958 | 2-Major | Reference to subsystem is lost after an update. | 4.1.00_SP2 | 4.1.00_SP4 | If an published subsystem is updated & there are other subsystem that depend on this published subsystem sometimes references in depending subsystems are nullified during the update. This can result in model check warnings/errors. |
|
| 30972 | 2-Major | Problem with fields of type double in German Locale | 4.1.00_SP2 | 4.1.00_SP4 | WebDataAttributes of type double or float may fail to validate when a different locale is used which uses comma as decimal separator instead of dot. Thsi problem is caused by the default Struts validator used for Double which apparently does not consider locale when parsing the submitted value. |
|
| 31119 | 2-Major | Class ApplicationFoundationModulePart missing from metamodel | 4.1.00_SP2 | 4.1.00_SP4 | ApplicationFoundationModulePart (AFMP) was removed from the metamodel and replaced by OptimalModulePart. This gives problems in existing AE courses and projects. |
A deprecated ApplicationFoundationModulePart has been added for backwords compatibility. A hotfix for this issue on 4.1.00SP3 is available through customer support. |
| 31227 | 2-Major | OJ app gives OutOfMemory exceptions in web-tier when deployed in JBoss via ASIT | 4.1.ITB1 | 4.1.00_SP4 | When an OptimalJ app is deployed to the bundled JBoss via ASIT, outOfMemory exceptions are thrown. This does not happen if the same application is deployed in a standalone JBoss. |
With this fix, ASIT starts a new JBoss JVM process with the same JVM memory settings as those found in a default JBoss 4.0.x installation: -Xms128m -Xmx512m |
| 29787 | 3-Normal | doc for joinpoint viewdataobject not updated | 4.0.00_SP6 | 4.1.00_SP4 | In OJ 3.3.01 the parameter "parent domain class" has been removed from the signature for the join point for VIEWDATAOBJECT in ViewDataObject.tpl in ipJavaApplication.jar |
Documentation has been updated to reflect this change. |
| 30903 | 3-Normal | Store by object property of webcomponent causes model check warning and generated form gives mapping error. | 4.1.00_SP2 | 4.1.00_SP4 | When changing the Store Mode from Store per set to Store per Object for an OptimalJ generated maintenance WEBComponent, some WebPageEvents under MaintBrowse webPage may get deleted accidentally, causing model check warnings and application errors at runtime. |
|
| 30965 | 3-Normal | Initial Layout Wizard for M1D layout does not show WebDataClass | 4.1.00_SP2 | 4.1.00_SP4 | The class is correctly retrieved and stored, but not shown on the panel. The problem only occures for the M1D layout-type |
Fixed |
| 31052 | 3-Normal | Customer Request <!DocType.xxx> attribute added to webtemplates | unspecified | 4.1.00_SP4 | The following JOINPOINT have been added: HTMLDOCTYPE(WebPage) HTMLDOCTYPE(WebTemplate) Both JOINPOINT generate a the following DOCTYPE by default: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> |
|
| 31139 | 3-Normal | OJ 4.1 SP2 and SP3 GA generates bad code for DAO using session beans | 4.1.00_SP2 | 4.1.00_SP4 | In a SessionBean class that uses DACs, compile errors are thrown for using non-existing methods from the UpdateObject class. This is a result of deprecating get/set methods only from DataObject class that previously had same names in both DataObject and UpdateObject. |
Resolved. |
| 31140 | 3-Normal | Relationships cannot be added to EJB deployment descriptor | 4.0.00_SP6 | 4.1.00_SP4 | There is a free block in the ejb deployment descriptor to add additional relationships. However this cannot be used because the free block is after the </relationships> tag. |
New freeblock has been added |
| 31149 | 3-Normal | Delegate code for retrieve does not trap errors on Date or BigDecimal attributes | 4.1.ITB1 | 4.1.00_SP4 | When using: - A retrieve using a query operation - A query field is of type Date parsing of the formbean string is needed to provide the Date. This leads to a NPE in the RetrieveAction Similar problems will occur when using date types like Time and Timestamp or other Class datatypes that need conversion. |
|
| 31160 | 3-Normal | Exception occures when you update all model. | 4.1.00_SP2 | 4.1.00_SP4 | Annotation: Exception occurred in Request Processor java.lang.RuntimeException: InvocationTargetException in DynamicInvoker.invokeMethod: invoked method was copyStructuralFeatures at com.compuware.repository.reflective.DynamicInvoker.invokeMethod (DynamicInvoker.java:207) at com.compuware.repository.reflective.DynamicInvoker.executeAllMethodsReversed (DynamicInvoker.java:135) at com.compuware.repository.reflective.RefCopyIncrementalContext.copyStructuralFea tures(RefCopyIncrementalContext.java:835) ... ... |
The cause of the symptom is that the copier expects that the type of a ReferenceView is a DomainClass, while it can in reality be a ClassView. * change to the product: Made the copier robust, which means that if the type is a ClassView, it searches the mapped schema of the viewed DomainClass. |
| 31185 | 3-Normal | A new model check message WEB014 is added | 4.1.00_SP4 | 4.1.00_SP4 | Model check message WEB014 needs to be documented | Documentation has been added |
| 30702 | 4-Minor | Problem list for weboutputtype does not clear out | 4.1.ITB1 | 4.1.00_SP4 | Once a weboutputtype problem is reported, it stays on the problem list forever, even after problem is fixed or offending model element is removed from the project. |
Fixed |
| 30988 | 4-Minor | generated code related to the styleClass attribute | 4.1.00_SP2 | 4.1.00_SP4 | There are a couple of CSS related issues that occur: 1. Unbound widget generate wrong HTML For certain widgets which are not bound incorrect HTML is generated. No class attribute is generated, but instead a Struts tag attribute styleClass is generated. This is visible as the CSS style is not picked up for these types of widget, so they have a different look from bound widgets. When the widget is bound a Struts tag is generated which is correct. In this case the eventual HTML is correct and the CSS style is properly processed. These problems occur for the following widgets: - WebButton - WebDropDownList - WebListBox - WebImage - WebRadioButton - WebPasswordField - WebUploadField When generating the preview page for a WebPage, no JSP is generated, but a direct HTML representation of the WebPage. Here also the styleClass attribute is generated rather than the class attribute. Here also this becomes visible by CSS style not being picked up. 2. Empty styleClass property The styleClass to be used by a widget is defined by the styleClass property. The styleClass property is not filled in by default for modelement types: - WebRadioGroup - WebImage 3. No CSS style defined No CSS style has been defined in the CSS file itself for: - webuploadfield - webimage |
1. Correct HTML is generated and the CSS style are picked up 2. The property styleClass is always filled in for widgets 3. The CSS styles have been added. |
| 30749 | 2-Major | NPE when creating a project with AppExport that depends on two other subsystems | 4.1.ITB1 | 4.1.00_SP5 | When trying to import an application export where the model has dependency on two other subsystems a NullPointerException occurs and it is not possible to import that project. |
fixed this issue by checking the repostory state before resolving dependent modules. |
| 31028 | 2-Major | Service copier is not incremental | 4.1.ITB1 | 4.1.00_SP5 | The copier sets a back reference for ReferenceViews with value-kind 'by value reused' which is wrong. In OJ 4.1, where polymorphism is not yet available, the reproduction is as follows: On the following class model Emergency -> SalesOrder(0..*)--(0..1)Customer <- VIP and ApplicationStructure 2tierFromService, update model ServiceFromClassPattern and set service.salesordersvc.SalesOrder.Customer.valueKind to by value (reused). If you change the type of service.salesordersvc.SalesOrder.Customer to service.customersvc.Customer then the regenerateProtected field (of service.salesordersvc.SalesOrder.Customer) gets value type, which is correct. After updating again ServiceFromClassPattern the regenerateProtected field service.salesordersvc.SalesOrder.Customer loses its value type. |
Fixed the Service copier. |
| 31138 | 2-Major | Query WebDataSchema attribute does not use WebInputType on domain attribute | 4.1.00_SP1 | 4.1.00_SP5 | A manually set style type is not considered by the code generator. This means that dates are always parsed according to the default dateformat and request locale. |
Changed the code generator to anticipate styletypes. |
| 31182 | 2-Major | WebComponent Maintenance and Browse have extra success-events in WebActions | 4.1.00_SP1 | 4.1.00_SP5 | WebComponents of the type HTML Maintenance and HTML Browse will have WebActions with one success-event too much. The event called 'success' should not be there. The event called 'success1' is correct, but it should be called 'success' (it is created later and got the extra '1' due to naming-rules) |
|
| 31187 | 2-Major | Query WebDataClass from WebComponent User-Defined is used in WebComponent HTML Maintenance. | 4.1.ITB1 | 4.1.00_SP5 | The WebActionFacade is to eager with initial values and checks. It needs that for the userdefined actions as the user may finish a wizard very early. |
Solution only affects the pattern-based actions and makes sure that for pattern-based actions setting the properties overwrites unwanted initial values. |
| 31612 | 2-Major | Exception while working with OJ | 4.1.00_SP4 | 4.1.00_SP5 | When drawing some lines in the UI designer following message occurs. It also occurs often when you are deleting many model items. java.lang.IndexOutOfBoundsException: Index: 35, Size: 35 at java.util.ArrayList.RangeCheck (ArrayList.java:546) at java.util.ArrayList.get(ArrayList.java:321) at com.compuware.repository.reflective.checker.ModelCheckLive ResultViewer$LiveResultListModel.getElementAt (ModelCheckLiveResultViewer.java:227) at javax.swing.plaf.basic.BasicListUI.updateLayoutState (BasicListUI.java:1154) at javax.swing.plaf.basic.BasicListUI.maybeUpdateLayoutState (BasicListUI.java:1105) at javax.swing.plaf.basic.BasicListUI.getPreferredSize (BasicListUI.java:356) at javax.swing.JComponent.getPreferredSize (JComponent.java:1615) ... |
Fixed. From multithread access on a list, the access is made synchronized. |
| 31821 | 2-Major | NPE when using an Attribute constraint with an attribute. | 4.1.00_SP4 | 4.1.00_SP5 | Using an Attribute constraint on a primitive type attribute with multiplicity 'zero or one' causes a NullPointerException in the EntityBean validateData method. |
Added check for a null object before the constraint comparison on attributes of primitive type with non- mandatory multiplicity, as it is done for the non- primitive attribute types. |
| 31168 | 3-Normal | EJB Code generation incomplete | 4.1.00_SP2 | 4.1.00_SP5 | Incomplete code is generated. By deviating from our standard service model 'byValue owned' to 'byValue re- used' a problem occured. The generated code is incorrect and the code generator doesn't take this into account. Variable declarations are missing. The problem is in the tpl that uses the SCHEMAWALKER tpl. This tpl works only on a DataClasses in one DataSchema. |
Changed the SCHEMAWALKER tpl to also find DataClasses from other DataSchemas for 'byValue' references and call it recursively for these DataClasses. |
| 31193 | 3-Normal | Reference value incorrectly set to null | 4.1.00_SP3 | 4.1.00_SP5 | In the following model, when storing the Reader session bean, reference value to the BookType is nullified, although in the code it is explicitly set. Reader(1)--(*)LogEntry(*)--(1)Book(*)--(0..1)BookType This is because of the store order of the beans. In the EntityBean method ejbPostCreate(), if a FinderException is thrown for one entity the rest of the code is not executed although it is a valid situation to ignore the exception since the object is being created. |
Surrounded the lines in the ejbPostCreate() method with a try-catch block which will ignore the FinderException, as it is done futher down in the code. Comments have been added to mention the reason of the "exception swallowing". |
| 31194 | 3-Normal | java.lang.StackOverflowError exception is thrown by OJ when WEBModules have cyclic dependency through usedModule property. | 4.1.00_SP2 | 4.1.00_SP5 | StackOverFlow Error occurs when WebModules have cyclic dependency through usedModule property. If a WebModule has another WEBModule as usedModule and this second one WEBModule has the previous one as usedModule, the cyclic dependency can result in StackOverFlow. |
|
| 31219 | 3-Normal | Request parameters not found in chained webAction when webPage contains an upload field | 4.1.ITB1 | 4.1.00_SP5 | When using attributes of type Image or Document webpages can use the upload widget. The result of this is that the encoding type of the page changes to multipart/form-data This is problematic when chaining webActions. This is when one webAction forwards to another webAction rather than to a webPage. In OptimalJ 4.1 every webPage gets a pageAction by default in which the formbean contents are copied back to the updateObject. After this the control is dispatched to the following action, for instance delete. When not using an upload field, the request parameters are still accessible in the chained action, but when using an upload field, the request parameter isn't accessible anymore. Reason for this is that a multipart request is used, this is to have a placeholder for the upload content. |
Fixed. |
| 31341 | 3-Normal | Generated code doesn't compile for action to delegate to consumed WS. | 4.1.ITB1 | 4.1.00_SP5 | When doing operation delegation on an operation problems can occur when the multiplicities of the delegator attribute and the delegate parameter are not in synch. The parameter mapping of the operation delegation maps between the delegator (source) and the delegate (target). The operation delegation wizard panel allows the user to map delegators to delegate if the data type is the same. Differences between multiplicities (0..1 and 1..1) are ignored here. This is not correct in case of primitive data typesand this will result in compile errors: Primitive data types values will be assigned to their class type equivalent without conversion. |
|
| 31493 | 3-Normal | DAC code generation issues with session components | 4.1.00_SP3 | 4.1.00_SP5 | When creating a BusinessMethod with return parameter of type ClassView and multiplicity 0..* compile error is thrown in the session bean class. This is beacuse of the extra code generated in the body of the BusinessMethod that should be there only for BusinessMethods that are mapped from DomainOperations with out/inout parameters of type DomainClass/DomainView. |
Add a condition in the EJB implementation of CreateUpdateObjectFromAutoKeyGen.tpl as it is done for the DAO implementation. |
| 31512 | 3-Normal | Incorrect constraint error when using dao and session bean. | 4.1.ITB1 | 4.1.00_SP5 | STORE operation using DAO with session bean incorrectly reports constraint errors when none exists. This is on custom webComponent. Default CRUD webComponent works fine. |
Added another condition in the constraint check that will give an error only when the existing Key and the UpdateObject's Key are different. The tpl is in CONSTRAINTSINGLEMANDATORYMULTIPLE. |
| 31534 | 3-Normal | Package tags are not published in a subsystem | 4.1.00_SP4 | 4.1.00_SP5 | A tag will only be published when its parent is an AlturaPublishable or an AlturaImplicitPublishable. Therefore a Tag in a modelpackage will never be published, because a modelpackage is neither of both. |
Fixed. In the SubSystemPublisher added the tag to the published list, after the modelpackages are added to the published list. |
| 31578 | 3-Normal | WEB072 message not present in help system | 4.1.00_SP4 | 4.1.00_SP5 | Documentation update required for bug 31341. | Documentation for model check message WEB072 added. |
| 31600 | 3-Normal | New model check message needed for pages with uploadfields | 4.1.00_SP4 | 4.1.00_SP5 | Documentation update required for bug 31219. | Documentation for model check message WEB919 added. |
| 31656 | 3-Normal | <!DocType.xxx> attribute bypassed in I.E. | 4.1.00_SP4 | 4.1.00_SP5 | When creating a userDefined webComponent the comment <!-- Additional page directions --> is added to the top of the final HTML right above DOCTYPE. This comment causes the DOCTYPE line to be ignored and a default DOCTYPE employed when using Internet Explorer. |
Changed the documentation to use JSP comments (<%-- comment here --%>). This means that the comment is not placed in the final HTML file so that the <!DOCTYPE> becomes the first element. |
| 31843 | 3-Normal | Non-compilable tracing code for MDBs | GA 3.0.00 | 4.1.00_SP5 | When "Logging code in EJB Tier" is set to 'Trace' instead of the default 'Info', the EJB IP might generate non- compilable logging code. |
Changed the TPL to generate correct logging statement based on the selected Queue or Topic. |
| 31441 | 1-Critical | OptimalJ crashes with SWTError when expanding ModelTree (with keypad-*) | 4.1.00_SP3 | 4.1.00_SP6 | OptimalJ could crash with an SWTError that OptimalJ ran out of handles. This could happen when a big model was used that contains a lot of badged elements in the domain or application view. (icons are badged or decorated when they have for example error markers or read-only decorations in the corner of the icon of a model-element) |
A cache has been introduced for badged repository element icons as well. This limits the number of created graphical SWT handles dramatically. |
| 31984 | 1-Critical | Error when starting OptimalJ (repository corrupted) after renaming modelpackage with case-insensitive same name | 4.1.00_SP3 | 4.1.00_SP6 | When renaming a ModelPackage into a name that is different when case-sensitive but equal when case- insensitive (like "lowercase" -> "LowerCase"), also while renaming it to something really different in between (like "somethingElse"), some repository files are not written to disk. How to reproduce: 1. Create new modelpackage (standard 3-tier structure with service). 2. Under the "service" create package "lowercase". 3. Update all models. 4. Close and reopen OptimalJ. 5. Rename "lowercase" to "LowerCase". 6. Update all models. 7. Close OptimalJ. The directory "lowercase" is empty, while serviceModelPackage.xcm refers to a "LowerCase" package. When restarting OptimalJ it complains about files it can't find. |
Two things were fixed: 1. OptimalJ should complain when it can't write a repository file. 2. When a directory with the same name but a case- difference exists, adapt the filename so it can be written; this algorithm worked OK for items stored in files (e.g. DomainClasses), but not for items stored in files AND directories (e.g. ModelPackages). |
| 32009 | 2-Major | New model checker message needed | 4.1.00_SP6 | 4.1.00_SP6 | Documentation update for model check WEB930. | Documentation updated. |
| 32324 | 2-Major | Association to supertype leads to svc model with by value cycle, which causes compile errors | 4.1.00_SP5 | 4.1.00_SP6 | Domain model with an association to a supertype gives code generation errors because of a byValue cycle. |
Added additional check for already traversed objects so that the loop doesn’t go in a cycle. |
| 31275 | 3-Normal | DBCS characters cannot be used for CICS Cobol field of type PIC X | 4.1.00_SP4 | 4.1.00_SP6 | It's impossible to insert both SBCS and DBCS characters in one COBOL field. |
The record framework now takes into account the fact that X fields can contain DBCS data when determining field and byte array lengths. |
| 31403 | 3-Normal | The retrieve action does not properly save and/or use the saved retrieve profile information. | 4.1.00_SP3 | 4.1.00_SP6 | The do_backward flag wasn't set by the user. It's not intuitive for the user to have to set this. the do_backward flag does two things: - It copies the query profile from the old formbean to the new one. - It uses cached data to show the list. |
Added a modelcheck (WEB932) to inform the user about having to use a backward flag. |
| 31519 | 3-Normal | it is not possible to modify the x and y properties of a widget contained in that panel unless the UIDesiger is open | 4.1.00_SP4 | 4.1.00_SP6 | X and y properties in the logical model are overriden by the presentation object. This is required under some circumstances in the absolute layout but not when the diagram is opening. As a consequence changes made in the logical model are lost when opening the diagram when first making changes to the property and subsequently opening the diagram. |
Fixed. |
| 31530 | 3-Normal | Erroneous JSP code generated for Master-Detail-Detail | 4.1.00_SP4 | 4.1.00_SP6 | An application (presentation side only) with one WebDataSchema and nested WebDataClasses which are more than one level deep does not work. When the application is launched an error occurs "Cannot find bean procedureSvcProcessSvcForm in any scope". |
Created a model check to inform the user that this is not supported. |
| 31566 | 3-Normal | a method definition is missing. | 4.1.ITB1 | 4.1.00_SP6 | if you have a A 1<>--* B 1<>--* C domain, and the C class contains a member of the type Document (BLOB). In the ABean a metod resolveBlob(Key):DataObject is generated that does not contain a method to resolve the BLOB of class C. |
The EJBFromClass copier is changed so that it adds all the composite parts (not only the direct first level part) to the usedServingAttributeList and usedComponentsList. In that way, the necessary methods for obtaining the parts beans are generated and they can be directly called for resolving the blob fileds in them (in EntityServedViewMethods.tpl). For DAO no change in the copier was needed, only one tpl file ResolveBlobInParts.tpl. |
| 31728 | 3-Normal | WebOutputType is ignored by the generator | 4.1.00_SP4 | 4.1.00_SP6 | Not all aspects of the WEBOutputType are being taken to account for user defined component. The formatting is used in the code, but typically the css style information isn't taken in account. |
It is now possible to incorporate the CSS style information from the WEBOutputType. The same is for the filter information. The impact is not so big as two templates mainly facilitate the addition of style information and other attributes. - In the case a WEBOutputType styleClass is detected this will override the style definition. - In the case a WEBOutputType style is detected this will override the style definition. In an earlier Service Pack a tag was added to facilitate the filterHtml attribute. This was light of the fact that WEBOutputTypes weren't supported for Userdefined components. As that has now changed the filterHtml can now be propagated from the WEBOutput type. For compatibility sake the tag will be left there, as long as it's taken care that the attribute doesn't come up twice. Not for all widgets a struts tag is generated, so non struts tags the filterHtml attribute aren't generated. |
| 31827 | 3-Normal | Context parameters return null values | 4.1.00_SP4 | 4.1.00_SP6 | The problem is caused by the fact that the page action uses the pre-4.1 style to update the ContextStack: ContextHandler.updateCurrentContext(request, className, roleName); |
Fixed |
| 31848 | 3-Normal | Problem tab in Eclipse is not refreshed when problem elements are deleted | 4.1.00_SP3 | 4.1.00_SP6 | The "Problem" Tab in eclipse contains a list of problems with the current application. If an element is deleted within the UI Designer in order to solve a problem in the problem list, sometimes the problem list is not updated and the problem remains in the list and Eclipse did not update the workbench.xml and the .markers file. So in some cases the problem tab has broken references, but in the repository everything is okay. |
The 'check all problems' action removes all existing model problems before checking the complete model. This ensures that the user does not have to handle a non refreshed problem tab. |
| 31870 | 3-Normal | Height property for Table Row is been ignroed by OJ. | 4.1.00_SP4 | 4.1.00_SP6 | The height property of a TableLayoutRow element doesn't propagate to the HTML that is generated. In fact there is no height attribute for the <TR> tag in HTML 4.01. It is actually supported by IE and Firefox, but it's considered to be proprietary. |
|
| 31980 | 3-Normal | Free block GEN-FREE gets overwritten during code regeneration. | 4.1.00_SP4 | 4.1.00_SP6 | Since 4.1 a page action is generated for every WebPage. The name for this action is <WEBComponentName><WebPageName>Action, so ChannelPartnerSearchAction Since there's a WebAction named SearchAction this will also create a file named ChannelPartnerSearchAction. |
|
| 32202 | 3-Normal | error 'Could not dereference object' when using date in associations. | 4.1.00_SP5 | 4.1.00_SP6 | In a model with association to a class that has Date as primary key, methods are missing in the Entity bean, so the ejb spec is violated. |
Fixed the tpl to generate the Date setters in the associated bean as they are generated in the main bean. |
| 32219 | 3-Normal | ConfigurableFactory cannot locate FactorySettings via EJB Container | 4.1.00_SP5 | 4.1.00_SP6 | ConfigurableFactory cannot locate FactorySettings when invoked from the EJB container. When Software Factory setting for Technical Keys is set to "long" both FactorySettings.properties in businessfacade and ejb are updated. But on deployment, the FactorySettings from ejb.jar can't be found and the default one is used. This is because the file is wrongly packaged in the jar file. |
Corrected the packaging in the ejb.jar file for FactorySettings.properties to be with the full path name, and not with the local file name like it's done for the other properties files. This has been corrected for both NetBeans and Eclipse. |
| 32308 | 3-Normal | Duplicate methods in webcomponent | 4.1.00_SP5 | 4.1.00_SP6 | This is caused by an error in TPL which results in duplicate methods for models containing classes associating the same class multiple times. |
Changed the TPL so that its generates only single instances of merge methods. This means that if you have added free block code in the duplicate methods before 4.1.00SP6, you will find this back in the recycle bin after using this upgarde. |
| 32326 | 3-Normal | Modelcheck WEB931 added | 4.1.00_SP6 | 4.1.00_SP6 | Documentation update for model check WEB931. | Documentation updated. |
| 32368 | 3-Normal | Rename Steeltrace in online help | 4.1.00_SP5 | 4.1.00_SP6 | Currently the documentation mentions Steeltrace as product name. As of release 4.1, steeltrace has been renamed to Optimal Trace. |
Renamed Steeltrace to Optimal Trace in the online documentation. |
| 32538 | 3-Normal | Helptext needed for new modelcheck | 4.1.00_SP3 | 4.1.00_SP6 | Documentation Update for model check WEB932. | Documentation updated. |
| 32568 | 3-Normal | Helptabs of Initail Layoutwizard outdated | 4.1.ITB1 | 4.1.00_SP6 | Help information updated |