Changelog for VP Suite 2.1 Build 20051204 (Dec 6 2005)

These changelog for VP Suite demonstrate the enhancements provided in the following products up to and including Build 20051204.

• Visual Paradigm for UML 5.1
• Smart Development Environment 3.1
• DB Visual ARCHITECT 3.0
• DB Visual ARCHITECT SQL 1.0
  

For XMI Importing, previously the DOCTYPE declaration defined in XMI will cause the file unable to be imported. For now, the DOCTYPE declaration will be ignored completely when importing an XMI.

In the previous build, if the default connector style was set to be “Rectilinear”, connector created from resource-centric interface would not stick to the center of the source shape.

After bug fixed:

In the previous build, the length of a stopped lifeline cannot be shorter than all other lifelines in the same sequence diagram. On the other hand, you were unable to create a lifeline that is longer than a stopped lifeline for its length. But for now, the length of stopped lifeline is adjustable, and can be adjusted freely.

After changed:

In the previous build, if you drag a diagram overview of an overview diagram towards the scroll bar, the preview content would be incorrectly painted on the scroll bar.

Before bug fixed:


After bug fixed:

When creating relationships between 2 entities, the FK will be created in the target automatically with %OPPOSITE_ENTITY_NAME%%OPPOSITE_PK_NAME% pattern. This judgment is case sensitive in the previous builds. But for now, it becomes case in-sensitive.

Before changed:


Since the letter ‘c’ for the word ‘Customer’ in Customer entity and customerID column in Account entity is not the same, a new column would be set up as the FK.


After changed:


After the change, it apply the customerID column as FK even it is of different case with the name of Customer entity.

In the previous build, if a dot net project contains spaces in its name, persistence code generated via ORM will have wrong file name.

After bug fixed:

Z-Order problems that occurred when moving a shape into a container have been fixed.

The ORM config file will now store correctly the column length defined in ERD.

In the previous build, importing an XMI that contains anchor model might cause the tool failed to import other models properly.

In the previous build, selecting Previous would not move to the prior diagram window, and selecting Next would not move to the next diagram window.

Before bug fixed:


After bug fixed:

Before bug fixed:


After bug fixed:

In previous build, if either side of a one-to-many relationship contained a composite key, the generated classes might have syntax error in following area:

• equal method
• Collection attribute not-null true
• toString with association
  

In the previous build, it would not allow user to generate database from an ERD that contains an entity with no tables. From now on, this action is allowed but with a warning message shows in the Message Pane.

A foreign key could be corrupted if it is referring to a column that does not exist. This would cause the DDL file unable to be executed. From now on, the corrupted foreign key will now be skipped when generating the DDL file.

Mistakes in driver file entry for applying DataDirect JDBC driver selection is fixed.

It will now detect whether a database driver file is available or not. A message will display if it is unavailable.

• Package name checking mechanism
  

For ORM, the package name will be converted to lower case before checking. If the name is checked to be a reserved word, code generation will be suspended.

• Not allow generating persistent class when using a Java/.NET reserved word as package name
  

In the previous build, user could generate persistent classes if any of the packages name is using a Java/.NET reserved word. However, the generated source files will cause a compilation error. Due to this reason, we will not allow generating persistent classes if any packages name is using a Java/.NET reserved word.

• Incorrect package name in source files
  

We would automatically convert the first character of package to lower-case upon generating persistent code. However, some of the source files might not follow this change but keep referring to the original package name. This problem is fixed in this build.

• Incorrect package name in ORM config file
  

We would automatically convert the first character of package to lower-case upon generating persistent code. However, information in ORM config file might not follow this change but keep referring to the original package name. This problem is fixed in this build.

• Compilation error for ORM persistent objects caused by package that starts with an uppercase character
  

In previous build, if an ORM Persistable class in put inside a package with a name starting with an uppercase character, the source code that is generated would cause compilation error.

• Compilation error for ORM persistent objects when association exists between 2 classes in different package

There would have several operations generated in a persistent class. Some of them accept parameters that reference another class. Before update, those references were generated without using full qualifier. After updated, those references will use full qualifier as classname.

The Visual Studio .NET user interface freezing problem that occurred when failed in generating persistent classes is fixed.