6.0.2
From Skyway Wiki
The following is a list of significant behavioral changes in Skyway Visual Perspectives Builder made in version 6.0.2
|
For a complete list of all issues that were addressed in this release, see this JIRA report (note: you will need to log in to JIRA to view the report) |
| Jira | Products Affected | Functional Area | Description |
|---|---|---|---|
| MOD-1091 | CE and EE | Facets | We versioned our code generation facets. After upgrading to 6.0.2 you should be prompted to upgrade each project. If you choose not to upgrade, or if the upgrade fails for any reason, you can recover by manually removing and re-adding our facet. To modify facets, right-click on your project in the Skyway Navigator and select "Properties". Then select "Project Facets". You can review all applied facets and Modify them using the "Modify Project..." button. Take note of which facets are applied. You'll need to remove them, save, re-open the dialog and re-add them.
|
| MOD-444 | CE and EE | Web Layer | We had a discrepancy in the style format accepted on the Change Style command versus the Style panel that appears on most web controls. In 6.0, the Style panel accepted standard CSS styles like: font-family: "Times New Roman", Serif; background-color: #FF0000; but the Change Style command (on the "Events" panel) required a JSON style like: {fontStyle: ‘italic’, backgroundColor: ‘red’}.
|
| MOD-1068 | CE and EE | Web Layer | A new validation rule was added to prevent an Action Mapping (specified in the Web Controller model) from having the same URL as either its View or Error View. For example, if you create an Action Mapping for the URL /index.jsp and also specified /index.jsp as the View, it would result in an infinite loop as the request would be routed through the Action Mapping again and again.
If you need to do this, a better configuration is to create a View Mapping (specified in the Project model) for /index.jsp and use that as the Action Mapping's View. For example:
|
| MOD-253 | CE and EE | Web Layer | When defining URL Action Mappings for a Web Controller, you can now specify (via a checkbox) that the controller use an HTTP redirect response to direct the browser to the View and/or Error View, as opposed to an internal forward.
Note: If you have existing Action Mapping definitions that use the "redirect:" prefix to force a redirect, you should remove the prefix and instead use the model attribute (checkbox). If the checkbox is applied to a View or Error View that includes the "redirect:" prefix, it will not work. |
| MOD-1254 | CE and EE | Library Updates | We updated from Groovy 1.5.4 to 1.5.6, Atomikos from 3.2.2 to 3.3.3, and our skyway execution jars to 6.0.2. You'll need to fix your build path for existing projects.
Also, if you're using MySQL with atomikos, make sure your MySQL driver is in the build path for your project. In prior releases it was acceptible to have the driver in the lib path of Tomcat, but no more. |
| MOD-1241 | CE and EE | Persistence | The new version of Atomikos required us to add a max pool size for your data stores. The Data Store editor's "Database Configuration" tab had a "Minimum connection pool size" field, but now we've added a "Maximum connection pool size" field. Both values default to 1.
|
| MOD-1282 | CE and EE | Pagination | In an effort to maintain consistency throughout the application all collection access will be 0 based. This mainly affects the functionality of the Starting Index field on the Property tab of the following steps:
ExecuteSQL Search Data Store Execute Named Query Prior to version 6.0.2, this field considered 1 to be the first record in the result set. From 6.0.2 on, this field now considers 0 to be the first record. For this reason, users will need to subtract 1 from any literal index value in this field. For example, if your Starting Index field had the integer literal 1 in it, you would need to change it to 0. Additionally, if the Starting Index field gets its value from a variable, wherever that variable is set should be checked to make sure that it takes into account that the index now starts at 0, instead of 1. The variable (or constant) could be initialized when declared as part of a conversation/operation/project. It could also be initialized/set in a Variable Editor or Groovy step.
|
