StreamBase 3.7 was the last release to use a structured project folder organization,
where certain file types had to be in certain folders, such as Resources. Support for automatically adding a folder named
Resources to the project's Resource Search Path was
dropped in StreamBase 6.4.0.
In the 5.x and 6.x release series, StreamBase Studio included a migration wizard that helped you migrate the structured folder organization of 3.x into the unstructured format of newer releases. In release 6.3.0, Studio stopped autodetecting a 3.x style project folder and automatically running the migration wizard, but you could still run the migration wizard manually.
Starting with release 7.0.0, the 3.x migration wizard is no longer provided with StreamBase Studio. If you still have 3.x project folders to migrate, use one of the following methods:
-
Open your 3.x project folders with a 6.x release of StreamBase Studio and run the 3.x project migration wizard. Then open your migrated folders in 7.x.
-
Follow the simple manual migration procedure described below.
EventFlow files from your 3.x project may not upgrade cleanly because of the significant semantic or syntax changes since 3.x. Open each EventFlow file in turn and resolve each typechecking error reported.
To manually migrate 3.x structured project folders to Studio 7.x, follow these steps:
-
Back up and preserve your 3.x project folders so that you can return to them for reference using Studio 3.7.
-
Create a new, empty project folder in Studio 7, adding Client API support in the New StreamBase Project dialog.
-
Import all files in your 3.x project folder using → → . Bring all files from the 3.x project's subfolders into the root of the new 7.x project folder, including any JAR files in the
Librariessubfolder. -
If you imported any JAR files, select each one, right-click, and from the context menu, run → .
-
If your 3.x project used any Java source code for custom operators, adapters, or clients, it was necessarily in a separate Eclipse project folder (not a Studio project folder). Use → → to import the Java code directly into your Studio 7.x project, using the Copy projects into workspace option.
In 3.x releases, JAR files were required to run Java operators, adapters, and custom functions, and such JAR files were always stored in the Custom Libraries subfolder. Recent Studio releases can work with the Java source files directly, and JAR files are not required. If you import a JAR file with your 3.x Java code and want to continue using it as a JAR file, then add it to the Java Build Path of the new project.