Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

THIS DOCUMENT IS NOT FINALIZED AND WILL BE UPDATED DURING THE 1.1 DEVELOPMENT PHASE.

Release Information

Version1.1.0.v20130529
TagR1_1_0_v20130529

New Features

Callback SystemThe services and network protocol gained a new feature. The "callback system". The server can call back to the client and request further information or confirmation. For example the logon process now can ask for a username and password. A write command ask for a confirmation dialog. So it also is no longer necessary to store the username:password information in the URI.
Authorization using PKI – PKCS12Using the new callback system openSCADA can also request the client to sign operations. The signature is done using the XMLSig standard. Using authorization rules, the server decides which operation needs to be signed. Adding signatures using PKC11 (like USB Tokens) is now only a small step which can be done in one of the next releases.

Enhancements

No more ".git" extension for checked out projectsSince git automatically removes the ".git" extension we changed our build scripts to respect that. It sure was easy to identify a git repository in the workspace by the ".git" extension. But we go with the default now.
Provide Target Platform FilesStarting with openSCADA 1.1 we will provide target platform files which make it a lot easier to set up an Eclipse workspace for openSCADA.
Enable API toolingWe tried it in the past. It was way too slow. We try again now.
Update external components

openSCADA 1.1 uses:

  • Eclipse 3.8.2: including EMF 2.8.3, GEF 3.8.2

Also we will remove/replace unused libraries. We will try to only use external bundles from the Eclipse Orbit repository.

Remove non-core bundles

There are some bundles which were needed in some customer projects, which might be useful for some other users, but are not really a core part of openSCADA (for instance all the spring integration bundles). They will not disappear, but will be moved to a contrib feature/repository.

See The "contrib" project

Clean up dependecies

Spring and its dependecies have all been moved to the contrib repository in order to clean up a mess of external dependecies.

Also the osgi.externprise bundle is imported now from Eclipse Gemini (http://www.eclipse.org/gemini/dbaccess/) instead of the one from openSCADA.

Bug Fixes

  • No labels