Servoy 7.x.x Documentation
Child pages
  • Upgrading to Servoy 7.x.x

Versions Compared

Old Version 22

changes.mady.by.user Paul Bakker

Saved on

compared with

New Version 23

changes.mady.by.user Paul Bakker

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Upgrading Servoy Application Server

As Servoy 6 7 is a major release a fresh Servoy Application Server installation is required.

...

Upgrading Servoy Developer

As Servoy 6 7 is a major release a fresh Servoy Developer installation is required. 

...

Upgrading existing Solutions to Servoy 6 7 is as easy as opening Servoy Developer 6 7 and getting the Solutions into the workspace . As Solutions that are opened in Servoy Developer 6 are updated automatically to be compatible with Servoy 6, they will stop being compatible with earlier versions of Servoy. It is therefor advised to checkout the solutions into a new workspace or import the solutions into the new workspaceor opening an existing workspace in Servoy 7. Note that once solutions are edited using Servoy 7, they cannot be used in earlier versions of Servoy anymore.

Once imported, the Solutions can be tested with Servoy 67. Servoy 6 7 introduces a few minor behavior changes, some of which could potentially break existing code. It should be investigated if the upgraded solutions are affected by these changes. The behavior changes are listed and discussed in the paragraph #Behavior Changes.

...

This paragraph describes the behavior changes that are introduced in Servoy 6.0. There are three categories of behavior changes:

  1. Changes that might break existing code
  2. Real behavior changes
  3. Changes that affect the display of the UI

Changes that might break existing code

  • Bugfix: JSFoundSet.getRecordIndex(JSRecord) now returns -1 instead of 0 when the record is not found, to be inline with other functions that return -1 to indicate "not found"
  • BugFix: When passing JavaScript Arrays into the Scripting API (Servoy Scripting API or plugins), previously empty Array positions were removed, now they are reserved
  • plugins.rawSQL.executeStoredProcedure() now returns the last resultset returned by the stored procedure, instead of the first, as this is most likely the resultset to continue with. 
  • In the solutionModel when asking for a specific element on a JSForm, if the element is not on the JSForm, the super form hierarchy will be inspected and return the element if the element in inherited. For the plural getElements() type of functions, an optional paramter has been added to include the inherited elements in the return value or not.
  • When adding a tableFilter on a column that already has a tablefilter on it, the newly applied filter will not override the existing filter, but the new filter will be appended, so both the existing and newly added tableFilter are in effect.
  • To implement the old behavior, the TableFilters need to be created with a name and then when applying a new TableFilter the old one needs to be removed through scripting.
  • BugFix: A bug was fixed that allowed making elements visible in scripting on which there was a security constraint that made the element invisible. The new behavior is that security takes preference over scripting for "visibility", like was already the case for "enabled"
  • The passing of deepLink arguments to the onOpen methods of both the Login solution (if applicable) and the main solution has been normalized:
    • Proper supports for deeplinks that specify multiple values for both the predefined "argument" parameter as well as custom named parameters. 
    • The difference between deeplinks using the full syntax ("arguments") or short syntax ("a") for specifying arguments has been made transparent: short syntax will be automatically converted to full syntax.
    • The query arguments in the URL that represent the solutionName or the methodName are filtered out, so only the real arguments are send into the onOpen method
      Examples:
      Code Block
      
http://domain:port/servoy-webclient/ss/s/{solutionName}/argument/1/m/{globalMethodName}/a/2/a/3/b/1/b/2/b/3 or
http://domain:port/servoy-webclient/ss?s={solutionName}&a=1&method={globalMethodName}&a=2&a=3&b=1&b=2&b=3 or
http://domain:port/servoy-client/{solutionName}.jnlp?a=1&a=3&b=1&a=2&b=2&b=3
      all results in the following arguments applied to the onOpen method
      Code Block
      
arguments[0]: 1
arguments[1]: {argument: [1,2,3], b: [1,2,3]}]

Behavior changes

  • In Smart Clients running under Java 6, Modal Dialogs (JSWindow of type MODAL_DIALOG and the dialogs displayed using the dialogs plugin) will be modal for their parent window (hierargy). This means that when having multiple windows (JSWindow of type WINDOW) open, a Modal dialog opened in one window will only block that window, not the other Windows. This aligns the behavior with the Web Client behavior. Unfortunately, the ability to set the scope of dialog modality in only possible from Java 6 onwards. When running Smart Clients on Java 5 modal dialogs will block all windows.
  • The position and dimensions of JSWindow's (Windows and Dialogs) are now persisted over client sessions
  • The client that gets started as Authenticator during the login process isn't consuming a license any more
  • controller.recreateUI() will keep the existing x and y scrollPosition of the form being recreated.
  • application.getTimeStamp() in the Web client will return the timestamp based on the timezone of the Client and the time of the Server: Before it would just return the timestamp based on the time and timezone of the server.
  • Tooltips in the Web Client are not shown immediately, but after a short delay, to synchronize the behavior between the Smart and Web Client. Note that through the UIProperties APP_UI_PROPERTY.TOOLTIP_INITIAL_DELAY & APP_UI_PROPERTY.TOOLTIP_DISMISS_DELAY the initial show delay and the dismiss delay are now controllable by the developer in both the Smart and Web Client
  • DeepLink arguments are now also applied to the onOpen method of the login solution. As a result of that, the application.getStartupArguments() method is deprecated, as it's no longer needed
  • Enhanced Security is now the default mode. The UI in Servoy Developer and in the Application Server to disable it has been removed. It is only possible to disable Enhance Security through setting the relevant property in the servoy.properties file: "servoy.application_server.enhancedSecurity=false"
  • All access to server side services like HeadlessClient or the Mail plugin is not allowed anymore from unauthenticated Smart Clients. In order to access serverside services, the user needs to log in first. If the solution requires access to a serverside service prior to the user logging in, the developer needs to expose the services as methods in the Authenticator solution, which can be accesses prior to the user authenticating.

Changes affecting the appearance

...

:

  1. Changes that might break existing code
  2. Real behavior changes
  3. Changes that affect the display of the UI

Changes that might break existing code

  •  

Behavior changes

  •  

Changes affecting the appearance

  •  

Resolving warnings and errors

...

Object

Deprecated method or property

Replacement

Comment

controller

.getContainerName()

controller.getWindow().getName()

 

Button
Label
Fields
Rectangle
TabPanel
SplitPane
Portal

.setBorder()
.setFont()
.getTitleText()
.setImageURL()

.border
.font
.titleText
.imageURL

Matching getters or setters added, allowing both getting and setting the value.
Not all mentioned properties are applicable to each mentioned type of object.
Due to a technical issue, Servoy Developer will yield a warning that the old setXxxx/getXxxx is undefined, instead of being deprecated. It will still work however.  

RuntimeLabel

.getParameterValue()

N/A

Never worked properly

Date

.setYear()

.getFullYear()

This function is deprecated in the JavaScript specification

Application

.getStartupArguments()

onOpen event handler of the solution

Deeplink arguments are now passed to both the onOpen event handler of the Login and Main solution.
The .getStartupArgument() is therefor no longer required to get access to the startupArguments prior to login

 

.closeForm()

JSWindow.hide()

Servoy 6 contains a complete new Windowing API. A window or dialog is now an instance of the JSWindow class to which a lot of the methods have been moved. New methods were added to the application and controller objects to interact with windows

 

.getWindowHeight()

JSWindow.getHeight()

 

 

.getWindowWidth()

JSWindow.getWidth()

 

 

.getWindowX()

JSWindow.getX()

 

 

.getWindowY()

JSWindow.getY()

 

 

.setWindowLocation()

JSWindow.setLocation()

 

 

.setWindowSize()

JSWindow.setSize()

 

 

.showFormInDialog()

application.createWindow('name',JSWindow.DIALOG).show('formName')
application.createWindow('name',JSWindow.MODAL_DIALOG).show('formName')

The method application.createWindow(..) returns an object of type JSWindow, which has an Scripting API to control additional things like the title, resizability, initial bounds and whether or not to show a textToolbar

 

.showFormInWindow()

application.createWindow('name',JSWindow.WINDOW).show('formName')

 

UICONSTANTS

.FULL_SCREEN

JSWindow.FULL_SCREEN

 

JSForm

.rowBGColorCalculation

CSS Row Styling & onRender event

 

JSPortal

.resizeble

.resizable

Fix typo

 

.rowBGColorCalculation

CSS Row Styling & onRender event

 

JSTabPanel

.onTabChange

.onChange

 

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="016edce8374d1e93-96b6ba09-43984117-afb49f0f-f905fdd79adfbd9de4bcf208"><ac:plain-text-body><![CDATA[

databaseManager

.getFoundSetDataProviderAsArray()

.convertToDataSet(['dataProviderId']).getColumnAsArray(1)

Duplicate functionality

]]></ac:plain-text-body></ac:structured-macro>

ServoyException

.INVALID_INPUT_FORMAT

N/A

never raised

plugins.file

.getHomeDirectory()

.getHomeFolder()

Match naming convention

 

.getRemoteList()

.getRemoteFolderContents()

Match naming convention

plugins.http

.createHttpClient()

.createNewHttpClient()

The HTTP plugin was refactored to support all types of HTTP Requests and support more finegrained control over the requests. Instead of creating an HttpClient and referencing it by name, the HttpClient is now an object with it's own set of methods, for example methods to create all the different types of HttpRequests. Each XxxxRequest object has a .executeRequest() function that returns a Response object again with it's own methods.

 

.deleteHttpClient()

N/A

No longer required

 

.getHttpClientCookie()

.getCookie() on HttpClient object

 

 

.getHttpClientCookies()

.getCookies() on HttpClient object

 

 

.getLastPageCharset()

replaced by .getCharset() on Response object returned by the .executeRequest() method on any of the XxxxRequest objects created by the .createXxxRequest() methods on the HttpClient object

 

 

.getPoster()

.createPostRequest() on HttpClient object

 

 

.put()

.createPutRequest() on HttpClient object

 

 

.setClientProxyUserNamePassword()

.setClientProxyCredentials() on HttpClient object

 

 

.setHttpClientCookie()

.setCookie() on HttpClient object

 

plugins.window

setToolBarVisible()

.setToolBarAreaVisible()

Name now matches what the function does

MenuBar
Toolbar

.validate()

N/A

No longer required

...