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 |
|---|---|---|---|---|---|---|
| 34015 | 1-Critical | The use of a non-incremental Web copier causes problems for team development | 4.2.ITB1 | 4.2.00_SP1 | - Usage of the new pattern (new development) in conjunction with the Integrated Team Development can result in unwanted results. - Customers working with applications migrated from 4.1 will not face this issue because they will use the OptimalJ 4.1 pattern which does not have this issue. EXPLANATION: during a model transformation (from domain to the web model) the web pages are replaced rather than (incrementally) updated when using the default OptimalJ 42 settings. When users synchronize with the version control system they will be confronted with model merge conflicts that should be resolved automatically. The user will then need to manually correct the resulting web page element which will contain duplicate elements. This will only affect customers who: a. Use the new default Web pattern, and b. Use integrated support for Team Development - Users who have migrated their OptimalJ4.1 application will not be affected, since a migrated application does not use the new web pattern. |
- We recommend customers using the new web pattern (new development) with the default OptimalJ 4.2 settings not to use Integrated Team Development until the fix for bug 34015 is available. - The 4.2.00 SP1 team development solution will contain a mechanism to handle the non-incremental web copier. Further explanation is provided in the user documentation: Using OptimalJ -> Team Development -> Version Control Concepts -> Model Merge Overview -> Special Model Merge Cases |
| 34119 | 1-Critical | Rename domain process and restarting OptimalJ results in corrupted model | 4.1.ITB1 | 4.2.00_SP1 | Rename domain process and restarting OptimalJ results in corrupted model |
Fixed |
| 34227 | 1-Critical | Webelements renamed after migration from OJ 4.1 to OJ .42 | 4.2.ITB1 | 4.2.00_SP1 | In 4.2 we enforce a new constraint on Web Model Element names, they must be unique with in the WebPage instead of unique withing a given WebPanel. This was to allow for shorter resource keys in property files. When migrating from 4.1 to 4.2, for any WebPage if it contains any Web Model Elements which have the same name they will be renamed automatically so that each element has a unique name. For example, in 4.1 it is possible to have two web labels with the same name so long as they are in different panels. This is a bug because the migrator was supposed to leave the names unchanged so that migrated 4.1 applications could be run in 4.2 without any naming changes. In that case you had the choice at a later time to migrate to the 4.2 naming convention by right clicking on the WebModule of the migrated application running in 4.2 and selecting and option to migrate to use short resource names (default for 4.2 applications). This optional migration is documented within the OptimalJ Help Contents: OptimalJ Professional Edition Guide -> Migrating From a Previous Version of OptimalJ. |
Issue fixed , renaming of web elements no longer occur during migration as of SP1. |
| 33688 | 2-Major | TeamDev (Eclipse/CVS) - Multi project import hangs sometimes if using a remote CVS repository | 4.2.ITB1 | 4.2.00_SP1 | TeamDev (Eclipse/CVS) - Multi-project import hangs sometimes if using a remote CVS repository |
Fixed |
| 33918 | 2-Major | Web code instantiate code generated for abstract classes. | 4.2.ITB1 | 4.2.00_SP1 | the cause of the symptom is that web code to create a new instance was generated for an abstract class, for which never a new instance (other than of its subclasses) should be generated. |
Fixed by making that code generation conditional, so that it only happens if the class is not abstract. |
| 33951 | 2-Major | Preview Web Page does not work | 4.2.ITB1 | 4.2.00_SP1 | Clicking "Preview Webpage" option results in error message to Console when using Architecture: JSP/Struts POJO/Hibernate. |
Fixed |
| 34013 | 2-Major | EAR files of used Hibernate subsystems are not always self-contained | 4.2.ITB1 | 4.2.00_SP1 | Deploying subsystems does not work in eclipse, classes cannot be found |
Adjusted IDE independent ModuleInfo classes for EJB and WEB modules to take using subsystems into account, and change the launching of the eardef compiler on eclipse. |
| 34022 | 2-Major | Runtime errors for generated WebFlows because of the same name used for WebPAge and WebAction. | 4.2.ITB1 | 4.2.00_SP1 | For a DomainService Operation a Flow is Generated together with a WebPage and WebAction. For the SinglePageMaintenance Component the generated Page has name <OperationName> instead of "<OperationName>Page". Because of this the generated code for the Page or the WebAction gets lost and on runtime user gets Blank pages. |
Fixed |
| 34043 | 2-Major | Enum in key gives NPE. | 4.1.00_SP6 | 4.2.00_SP1 | When the key of an object contains an enumeration type, the JSP does not correctly send a selected object in a list. It sends the value whereas the receiving Select action expects the name. This becomes apparent in the Select action. |
Fixed |
| 34089 | 2-Major | NetBeans multilanguage import fails | 4.2.ITB1 | 4.2.00_SP1 | In NetBeans multilanguage UML import fails | Fixed by bundling xalan 2.6.0 instead of 2.5.2. |
| 34102 | 2-Major | Changes to domain attribute constraints (regular expressions or ranges) via the wizard are not stored in the model | 4.2.ITB1 | 4.2.00_SP1 | While using the wizard to edit the values of attribute- constraints (regular expressions or ranges), OJ will not catch the new values but keep persist to have the previous values. |
|
| 34114 | 2-Major | NPE when generating code after importing EJB | 4.2.ITB1 | 4.2.00_SP1 | After importing a legacy EJB and then generating code a NPE occurs. |
fixed jarroot resolving in Eclipse based version. |
| 34182 | 2-Major | TeamDev - Model changes no longer persisted after Team->Update OptimalJ Models with a diagram open | 4.2.ITB1 | 4.2.00_SP1 | TeamDev - Model changes no longer persisted after "Team- >Update OptimalJ Models" with a diagram open |
|
| 34210 | 2-Major | properties environmentSupportsManaged* are not described correctly: only generic text exists | 4.2.ITB1 | 4.2.00_SP1 | fixed | |
| 34217 | 2-Major | New Child menu on TP module displays "bogus" | 4.2.ITB1 | 4.2.00_SP1 | When using the the context menu on a technology pattern module in the software factory model, the menu sometimes shows "bogus" instead of a list of elements. |
Fixed |
| 31167 | 3-Normal | Enhancement requests for "enabled" and "visible" property of web tier | 4.0.00_SP6 | 4.2.00_SP1 | Following features should be enhanced: - "visible" property added to web page elements including panels. This property would allow run-time hiding of element the same way as "enabled" property conditionally disables them. - Improved Property editor for "enabled" and "visible" which would allow picking attributes (from different scopes including request) as property value. Or maybe even would allow creation of simple logical expressions for these properties." |
done. |
| 33085 | 3-Normal | Terminology in EntityClass wizard regarding operations unclear | 4.2.ITB1 | 4.2.00_SP1 | HTML help text contained a word that is too long for the wizard panel (HTML viewer) to display |
Fixed by adapting HTML helptext. |
| 33121 | 3-Normal | pageiterator buttons duplicated when using scriptlets | 4.1.00_SP6 | 4.2.00_SP1 | Web components have property jspTagLib. The default value is Struts/JSTL and the alternative value is Struts/Scriptlets. If the latter option is chosen no JSTL (JavaServer Pages Standard Tag Library) tags (like <c:if ... /> should be generated. Instead the generated code should use appropriate jsp in order to achieve the required functionality. Setting the jspTagLib property to Struts/Scriptlets still generates JSTL code in some jsp locations. One resulting problem is the webpanel for the page iterator in a user defined web component (with code generation option jspTagLib set to "Struts/Scriptlets") having a “Prev” and a "Next" button. In the generated jsp the references <%@ taglib uri="http://java.sun.com/jstl/core" prefix="c" %> <%@ taglib uri="http://java.sun.com/jstl/fmt" prefix="fmt" %> To the appropriate tag libraries are not present which is OK. However, the JSTL tags <c:if …./> are still used for enabling or disabling the “Prev” and “Next” buttons. What happens in this case is that on runtime the expectation is that one sees one “Prev” button and one “Next” button, either or not disabled. On the actual page however you see a disabled prev button an enabled prev button a disabled next button an enabled next button. This is wrong. Another location where still JSTL tags are generated in the scriptlet case is alturaTemplate.jsp. |
Two "previous" and two "next" buttons are displayed if you choose Struts/Scriptlets. Reason is that for enabling/disabling <c:if> are used and the import <%@ taglib uri="http://java.sun.com/jstl/core" prefix="c" %> is missing. If you use scriptlets this should only affect the iterator logic. This means that the <c:forEach> is replaced with scriptlet code <% for(...) %>. This is mainly because of performance reasons (which we have to verify again if this is still the case). As a solution, we added the import statement. |
| 33613 | 3-Normal | error message is rather cryptic when using Domain Attribute Constraint | 4.2.ITB1 | 4.2.00_SP1 | When you entered invalid data according to a Domain Attribute Constraint , then the error message is rather cryptic in the architecture J2EE with JSP/Struts, session beans and POJO on Hibernate , while in the architecture Lightweight application with JSP/Struts and POJO on Hibernate a more clear message is given. |
Message adapted |
| 33820 | 3-Normal | Data Binding wizard Authorization panel sometimes only shows webButtons | 4.2.ITB1 | 4.2.00_SP1 | The data binding wizard Authorization panel sometimes filters out all widgets apart from WEBButtons, and displays them with the WEBLabel icon. |
Fixed |
| 33949 | 3-Normal | Cannot model constraint on IP Module | 4.2.ITB1 | 4.2.00_SP1 | According to OJ Help you should be able to add a Constraint model element to an IPModule element in the Software Factory Model. However when you select my IPModule and choose new, you do not have the option to add a Constraint. |
fixed |
| 33954 | 3-Normal | Some JSPs are generated with invalid tag matching | 4.1.00_SP6 | 4.2.00_SP1 | Some JSPs are generated with invalid tag matching. Specifically, for webComponents based on domainServices which are based on subtypes have their default browse JSP created with a <td> without a closing </td> |
Fixed |
| 33971 | 3-Normal | enumeration literals need to have char values | 4.1.00_SP5 | 4.2.00_SP1 | If you have an enumeration of type "char" the enumeration literatals need to have char values. '\u0002' would be a perfectly valid value here, but OptimalJ gives model check errors in the domain model and in the application common model. This is because it only checks for the length of the value. |
Fixed by better checking the size of the string (taking Unicode and special escaped characters into account) |
| 33995 | 3-Normal | in grid, th and td have style="webgridcolumn" - should be class= | 4.2.ITB1 | 4.2.00_SP1 | Wrong HTML code is generated for the styleClass property. | Fixed |
| 34025 | 3-Normal | Topics about business operations in Web tier not present in helpset | 4.2.ITB1 | 4.2.00_SP1 | Documentation for operation delegation type support in the Web model is incomplete. |
Documentation is updated for improved type support in the Web model. |
| 34038 | 3-Normal | Debugging info shown in Output tab when generating code for an AA or TP Module | 4.2.ITB1 | 4.2.00_SP1 | If the file is not generated (which is OK in the case of TP and AA modules) a NetBeans FileObject is accessed that does not exist. This leads to a CATCHED NPE. This NPE should NOT be visible for the end-user. It should be silently ignored. |
debuginfo suppressed |
| 34105 | 3-Normal | Model2Code view is continuously refreshed during Update All Models | 4.2.ITB1 | 4.2.00_SP1 | Fixed | |
| 34118 | 3-Normal | Transient attributes should generate free block in get/set of POJO | unspecified | 4.2.00_SP1 | In order to create a derived property (e.g. totalPrice that multiplies the quantity with the price of a shopping cart item) it would be very handy if at least the get<TransientAttribute> has a free block. Currently it is guarded, which makes it more difficult to create derived properties and use them in Web. |
Fixed by adding free block. |
| 34133 | 3-Normal | To have icon in UI designer for HTML Importer in 4.2 - Changes needed to Xenon Web Diagrams module and Web Module | 4.2.ITB1 | 4.2.00_SP1 | In order to use the HTML-Importer, delivered on Pattern Plaza, we need to add a button to invoke the importer from within the UI designer. |
Fixed by adding a dynamic button that will appear if the HTML-Importer is installed. |
| 34206 | 3-Normal | Document Testing and Deployment of Subsystems with DACs / Entity Classes | 4.2.ITB1 | 4.2.00_SP1 | Full separation of subsystems at development and deployment is only supported for EJBs - DACs and entity classes have limitations that should be documented. (see also software issue 34013). |
documentation implemented. |
| 34229 | 3-Normal | No support for editing oneToOneForeignKeyMapping property | 4.2.ITB1 | 4.2.00_SP1 | The 'oneToOneForeignKeyMapping' property in DBMSFromClassPatternOptions is to allow for correct RDBMS mappings in the case of one-to-one bidirectional associations. All non-Hibernate application architectures require that this property have a value of 'Foreign key on both sides' while all Hibenate-based architectures will only work if the property has a value of 'Foreign key on one side only'. To ensure that the user doesn't inadvertently change the property's value it has been made read-only. |
Property has been marked read/write again, to facilitate the documented migration path to using hibernate persistency. |
| 34310 | 1-Critical | Wizard code generated on wrong location when generating from commandline | 4.2.ITB1 | 4.2.00_SP2 | When running the WizardIP generator TPL from the build.xml file (commandline), the code is generated in the wrong location. It is generated in the pluginroot i.s.o. in the uipluginroot. The problem is that the JarRoot was not set into the TPLContext by in the IP preinvoke. |
Added preinvoke calls to WizardIPModuleModule.java |
| 34109 | 2-Major | Reference to mapping file of transient classes generated in hibernate config | 4.2.ITB1 | 4.2.00_SP2 | definitions for transient classes are no longer generated. | |
| 34157 | 2-Major | CVS tutorial issues | 4.2.ITB1 | 4.2.00_SP2 | The Team Development tutorial contained errors. | The tutorial is repaired. |
| 34163 | 2-Major | Names for assocations and association ends are ignored by UML class importer for MagicDraw | 4.1.ITB1 | 4.2.00_SP2 | Labels for associations and association ends are not imported into the domain class model. Instead the importer generates default names for association and association ends. |
Fixed in the MagicDraw xslt script. |
| 34369 | 2-Major | servlet 2.3 web.xml is invalid for lightweight architecture | 4.2.ITB1 | 4.2.00_SP2 | With lightweight architecture and servlet 2.3 the genenerated web.xml is invalid with respect to its dtd and this makes WebSphere deployment fail. This is caused by filter and filter-mapping elements that are intermixed (which is valid in the Servlet 2.4 specification). |
Changed the generation order, to first generate all filter elements and then all filter-mappings. |
| 34447 | 2-Major | Converting a 4.1 Application to Hibernate Arch | 4.2.00_SP1 | 4.2.00_SP2 | If the model is based on a DBMS import which has been copied to the domain model, the technology pattern creates domain elements from 1 source element in the dbms model. After the domain model has been created the Entity model is created, this technology pattern does not take into account that both DomainAssocionEnds of a DomainAssociation can 'link' to (the same) ForeignKey. The EntityFromClass technology pattern has to be more intelligent. |
Let the EntityFromClass technology pattern use a more intelligent method to find the ForeignKey in the dbms model. For associations with a Relation Table the ForeignKey must be in that table. For other associations the ForeignKey must be in the 'own' table. What will not work is: use the DomainUtil.isAssociationOwner. For example for many - many associations it returns only true for one of the associations sides, while the ForeignKey needs to be found for both association Ends. |
| 33669 | 3-Normal | .cvsignore file missing in <installdir>\docs\tutorial\ignorefiles | 4.2.ITB1 | 4.2.00_SP2 | The sample .cvsgnore file is missing from some installations of optimalJ. |
The missing file is now restored. |
| 33837 | 3-Normal | Cannot store record after key validation error | 4.2.ITB1 | 4.2.00_SP2 | If you create an invalid key (alpha in numeric field, for instance), the key fields are grayed-out and can no longer be edited. |
The root cause of the problem is that the "in create mode" state of the FormBean was not being copied over during merge, which resulted in the state of "in create mode" being lost after a validation error. Fixed by adding a simple one-line piece of code to copy over the "in create mode" state during merge along with the other attributes that are copied over. |
| 34160 | 3-Normal | Switching workspace in Eclipse results in license error | 4.1.00_SP4 | 4.2.00_SP2 | Steps to Reproduce: 1) Start OptimalJ Eclipse using license with one user, i.e., with tag: <Count>1</Count>; 2) Switch workspace; Observed behaviour: Popup window shows up with error message: No valid license found; The licensed number of concurrent users has been reached; try again later. |
Fixed by integrating DLM4108, where it has been fixed. |
| 34169 | 3-Normal | Generation Code console window is not very descriptive and it is hard to notice it there are errors. | 4.2.ITB1 | 4.2.00_SP2 | It should be more obvious that your implementation pattern has errors instead of just message in the console. Proposal is to have a (modal) dialog popup that the user has to click away to proceed. |
Implemented |
| 34213 | 3-Normal | Architect edition migration documentation needs improvements | 4.2.ITB1 | 4.2.00_SP2 | The migration documentation should describe the following for AE migration: 1 - Remove all generated JAR files from the project before migrating. 2 - The migration documentation does not show changing the SFD file. |
Documentation updated. |
| 34223 | 3-Normal | unclear procedure in "Migrating Architecture Edition Projects" | 4.2.ITB1 | 4.2.00_SP2 | The AE migration documentation should make clear the migration is based on mount points and not application exports. |
Documentation updated. |
| 34267 | 3-Normal | Proper icons are missing in the Architect Edition | 4.2.ITB1 | 4.2.00_SP2 | For the following metaclasses proper icons are missing. ArchitectureModule ApplicationArchitecture ApplicationArchitectureOption TechnologyPatternOption SoftwareFactory License |
New Icons have been created. |
| 34290 | 3-Normal | Domain parameter of type DomainClass results in compile errors | 4.2.ITB1 | 4.2.00_SP2 | A domainOperation with parameter of type DomainClass results in a compile error in the presentation tier, when the applied application architecture is lightweight. |
Fixed |
| 34343 | 3-Normal | Using a webtemplate from a used subSystem is not included in using war | 4.2.ITB1 | 4.2.00_SP2 | When a WEBTemplate from a used subSystem is used in a using subSystem, the assembled war file of the using subSystem does not contain all artifacts pertaining to the used WEBTemplate. |
Templates (and css and images for that matter) from a published subsystem are now copied to the deployed war file and are therefore now accessable to the main module. |
| 34374 | 3-Normal | OJ 4.2 NetBeans GA and SP1 contain 4.1 version PDF | 4.2.00_SP1 | 4.2.00_SP2 | In OptimalJ 4.2, it was decided to no longer deliver tutorial PDF files. Due to a packaging issue, the OptimalJ 4.1 PDF file was shipped and installed with OptimalJ 4.2 (netbeans editions). |
PDF file has been removed from the distribution, as well as the menu item pointing to it. |
| 34405 | 3-Normal | styleId generated instead of id: field not usable in javascript and CSS. | 4.2.00_SP1 | 4.2.00_SP2 | The generated code in the jsp contains something like: <img src="<bean:write name="domainClassDomainClassForm" property="myattr"/>" class="webimage" styleId="DomainClass.myattr"/> This code contains styleId instead of id. The result of this is that certain javascript (e.g. getElementById()) and CSS (#mycssclass {...} definition) references are not possible anymore. |
Fixed |
| 34409 | 3-Normal | Dropdown information lost after server validation failure | 4.2.00_SP1 | 4.2.00_SP2 | When you enter new record without entering data and try to enter second record - OJ lost all the drop down values. When creating a new record, loadCandidateValues() is called, setting up the dropdowns. When there is a validation failure, the page is redirected back and this is not called. |
Instead of generating loadCandidateValues in the create action and after a failed validate, the loadCandidateValues has been moved to the loadBean and mergeBean methods, which fixes UserDef and Hibernate equally and is more easily maintained. |
| 34472 | 3-Normal | bind a WebTab to a WebDataAttribute | unspecified | 4.2.00_SP2 | Currently web tabs cannot be bound to WebDataAttributes. This is because the wizard does not consider it a valid data binding. Furthermore the jsp rendered for the web tab element does not support rendering of data attributes (only web tab labels). |
Implemented. |
| 34473 | 3-Normal | bind widgets to corresponding attributes in WebDataclass | unspecified | 4.2.00_SP2 | problem trying to bind widgets to attributes in a WebScopedContext. In the data bindings wizard, if you have a WebScopedAttribute with a type of WebDataClass you can bind to the WebScopedAttribute but not the dataAttributes of its type. |
Templates do now allow binding to the scoped attribute itself which was a problem with the wizard whereas WebPages allow such a binding. |
| 34404 | 4-Minor | webImageSrc declaration not necessary with String field | 4.2.00_SP1 | 4.2.00_SP2 | A Domainclass attribute of type String results in the generated jsp page in the declaration of: <% String webImageSrc="/DomainClassGetBlob.do?blob.field=myattr"; %> This is only necessary when the domain attribute type is Blob, not with String. |
Moved the code that creates the WidgetIdSrc variable into the scope of the code that is used so that it's not generated unnecessarily. |
| 34250 | 1-Critical | AE: Changes to implementation property field not saved | 4.2.ITB1 | 4.2.00_SP3 | When editing the implementation property of an object in a metamodel mutliple times the implementation isn't saved after the second time. |
|
| 34353 | 1-Critical | Deadlock after deleting model element from Domain Explorer | 4.2.ITB1 | 4.2.00_SP3 | A deadlock may occur when OptimalJ is opened with multiple diagrams open, when (in the explorer) the element is deleted that the currently active diagram represents (which leads to the deletion and closing of that diagram), if the diagram behind it has not yet been activated. |
|
| 33272 | 2-Major | Starting sample app on WebLogic 9.1 or WebSphere 6.0.2.9 with DPJ enabled fails to actually enable DPJ | 4.2.ITB1 | 4.2.00_SP3 | DevPartner for Java profiling is not enabled when using BEA Weblogic or IBM Websphere with OptimalJ Eclipse editions. |
Fixed |
| 34383 | 2-Major | Rootpackage created under wrong project | 4.2.00_SP1 | 4.2.00_SP3 | Creating a new root package under a second meta modeling project, creates the package under the first project. |
Fixed. |
| 34418 | 3-Normal | Model check errors when creating Webdatachema | 4.2.00_SP1 | 4.2.00_SP3 | In very specific scenarios when using a Domain model from a read only subsystem and where the DBMS model is also part of that readonly subsystem, creating a WEBDataSchema using the WEBDataSchema wizard and including some of the extra associations as byValue (owned) instead of default byReference may result in an incorrect WEBDataSchema. |
The code tried to delete some elements in the readonly subsystem. This problem is fixed now. |
| 34609 | 3-Normal | Oracle schema fails with NPE instead of detailing the cause of failure | 4.2.00_SP1 | 4.2.00_SP3 | When importing an Oracle schema, and selecting too few classes to resolve all foreign key relationships, the OptimalJ importer fails with a NullPointer exception, without importing anything. |
Fixed. No Null pointer is thrown anymore. When the importer cannot resolve a foreign key, it will ignore it and continue importing. Consequently, the resulting model will not have the references to the tables that this foreign key was referring to, nor will it contain these foreign keys. |
| 34611 | 3-Normal | Creating a new association table data fails with store error. | 4.2.00_SP1 | 4.2.00_SP3 | Upon creation of an updateobject with an composite key containing keyattributes representing the associated object its key value, these fields must be initialized with null values. Currently this is not the case as these fields are initialized with BigDecimal(0). The result is that the businessfacade attempts to retrieve the associated objects which fails. |
The default implementation of the create<X>Key() method in the CreateAction is modified to intialize above mentioned keyattributes with null. |
| 34612 | 3-Normal | Manual update of presentation model takes a lot of time on various edit pages | 4.2.00_SP1 | 4.2.00_SP3 | In case you have a huge model, where classes have a huge amount of relationships, the Web Page layout copier takes very much time to generate the page layout. |
The performance bottleneck that caused this issue has been resolved. Performance gain can be 50-70% on very large models. |
| 34614 | 3-Normal | CLOB fields changed to 'no value' after importing Oracle schema. | 4.1.ITB1 | 4.2.00_SP3 | CLOB field is not recognised by our dbms importer, this ia caused by the Oracly driver which identifies the type of the Column as: OTHER |
Fixed in Oracle importer specific code. |
| 34679 | 3-Normal | EntityAttribute does not set initial type | 4.2.00_SP2 | 4.2.00_SP3 | A model check error should be shown when an EntityAttribute doesn't have any type set. |
Modelcheck APP027 has been implemented to catch this situation. |
| 35009 | 2-Major | cannot create the Entity Model. | 4.2.00_SP2 | 4.2.00_SP4 | The Model Copier failed with java.lang.RuntimeException Invalid Situation. This issue only occured in a situation where you import a dbms model from an existing database. |
Fixed |
| 35098 | 2-Major | NPE When using attributes of type Date / Enum for Operation Delegation in Operation Action | 4.1.ITB1 | 4.2.00_SP4 | When using the Operation Action to delegate to a BF operation the parameter of type Date / Enum are not checked for null. This means that when copying data from the form bean to the update object the form bean attributes are converted to a Date / Enum without checking if the form bean attribute contains a value. This can cause problems because certain information can be displayed as readonly on the page. |
Before copying form bean attribute to the UpdateObject we now check if the form bean attribute is not null. |
| 34697 | 3-Normal | Single page edit or adding new record gives error msg in OJ when using Hibernate | 4.2.00_SP2 | 4.2.00_SP4 | The code for update Single Valued Association on submit of a page uses UpdateObject method fromKeyClass to create an Update Object and set it to the parent update object. When doing this the CRC value is set ot 0, which is apparently not usable for these purposes. In the past for DACs and EntityBeans this case was checked explicitly and ignored but this is not possible for Hibernate. |
Fixed. A new utility method is provided on the UpdateObject API which takes UpdateObjectComparable object and does not need creation of an UpdateObject before assigning it to the parent Object. |
| 34780 | 3-Normal | A new model check (APP027) has been added and doc is needed | 4.2.00_SP3 | 4.2.00_SP4 | In OptimalJ 4200SP3, a model check was added, but no documentation yet. |
A message for the model check is added to the online documentation. |
| 34904 | 3-Normal | No OptionsCollection generated in JSP when binding a WebListBox (instead of a Dropdown list) | 4.2.ITB1 | 4.2.00_SP4 | Create CRM example 3tier. Modify CustomerSvc WebComponent and add additional UsedServingAttribute ServiceAgreementSvc. Add a dropdown list on the Edit page for selecting ServiceAgreement and bind it to Customer.serviceAgreement WEBdataReference. Generate code, deploy and test that it all works. Replace Dropdown list with Listbox. Observed behaviour: List is empty when deployed. The optionsCollection tag within the Select Tag is not generated. |
Changed userdef/widgets/RenderWEBListBox to generate an optioncollection under mentioned circumstances. |
| 34906 | 3-Normal | Wrong property name in JSP when using Listbox for an attribute with high multiplicity | 4.2.ITB1 | 4.2.00_SP4 | An attribute (dummy or transient or based on OperationParameter) with high multiplicity, bound to a WebListBox, generates unusable JSP code. THe generated JSP Code refers to propertyname selected<AttrName> instead of <AttrName>. |
Fixed |
| 34990 | 3-Normal | JDBC Import gives error when importing tables with unresolvable foreign keys | 4.2.00_SP1 | 4.2.00_SP4 | In some situations, when you limit the number of tables to be imported in the DBMS model, the dbms importer makes wrong assumptions on the table from which a foreign key field should be resolved. |
Fixed. |
| 35133 | 3-Normal | After importing table definition from DB2 and then generating Domain model, then adding an Entity model and doing Update all model follwed by Check all model, attributes which refer to DB2 Column of type CHARACTER in the DB2 result in errors in the Entity Model. | 4.2.00_SP3 | 4.2.00_SP4 | After importing table definition from DB2 and then generating Domain model, then adding an Entity model and doing Update all model follwed by Check all model, attributes which refer to DB2 Column of type CHARACTER in the DB2 result in errors in the Entity Model. |
Made the ENT037 model check a bit more relaxed. Furthermore, added a new mapping to HibernateUtil, so that it knows that Java.lang.String and CHAR map to Hibernate type 'string'. |
| 35169 | 3-Normal | Edit WebInvocationNode Wizard runs as Create wizard | 4.2.ITB1 | 4.2.00_SP4 | When editing a WebInvocationNode in order to select a different usedFLow, the wizard first asks for a Flow where to create the invocation node in. However, that is already known as Node exists. Also this confuses users as the next dialog is also about selecting a WebFlow (usedFlow). The cause of this is that the wizard is started in Create mode and not in edit mode. |
Fixed to start the wizard in edit-mode. |
| 35283 | 3-Normal | Not possible to select WebTemplate from published/used subsystem. | 4.2.ITB1 | 4.2.00_SP4 | It is not possible to select a WebTemplate from a published subsystem in WEBComponent and WebPage wizard. |
Fixed |
| 34746 | 4-Minor | OJ reports earlier version after deinstall and reinstall in same direcectory | 4.2.00_SP2 | 4.2.00_SP4 | When you uninstall OptimalJ (Eclipse Edition), and reinstall in the same directory, OptimalJ seems to suffer from cached plugins, and therefore might not use the newer version of the plugins. |
The cached plugins were located in a configuration directory in <installpath>/eclipse/configuration. This directory will be removed explicitly after uninstalling OptimalJ 4.2.00SP4 or higher. This means that if you install OptimalJ 4200SP4, you will not yet benefit from the change (which is at uninstall time), and need to manually execute the workaround. |