Package Explorer

StreamBase Studio's SB Authoring perspective includes a Package Explorer view for navigating projects. When you create a new StreamBase project by selecting New → Project from the File menu, or by clicking the New StreamBase Project button () in one of the toolbars, that project will appear in the Package Explorer as a folder.

Project Resources

Each project folder contains your StreamBase application files and any resource files required by your applications. Your project folders can include the following types of files:

  • EventFlow application files, with sbapp extension.

  • StreamSQL application files, with ssql extension.

  • Feed Simulation control files, with sbfs extension.

  • Data files, such as CSV files, that provide input tuples for feed simulations.

  • Recording files, with sbrec extension. These contain recordings of running StreamBase applications that capture data streamed onto the application's input streams.

  • StreamBase Server configuration files, with sbconf extension. These files change default configuration parameters for running your application. For more information, please see Defining a StreamBase Server Configuration in the Administration Guide.

  • A java-src and JRE System Library folder. These folders are inherited from Eclipse, and serve as source folders for the root of packages containing Java files. Library folders contain JARs and classes.

  • Custom library files, including DLL, .so, and JAR files, that contain custom functions, operators, and aggregates.

  • JAR files that you create. To use the StreamBase Java Client API in your project, you must add the StreamBase Client API to your project's Java Build Path. See StreamBase Project Properties for details.

You are free to import or create files other than those we have listed. You can create folders in your project to organize your resources as you need to.

Context Menus

The standard Eclipse context menus (the right-click menus) are available for each file and most folders in the Package Explorer. Some StreamBase-specific commands are also available, and appear according to the currently selected file type. Commands that are not StreamBase-specific perform the standard Eclipse functions.

  • New

    This context menu duplicates the top-level File → New menu, which is described in Menu Reference.

  • Open

    Opens the selected file in the editor area of the SB Authoring perspective, using the default associated editor. StreamBase provides a number of specialized editors for different files. For example, an sbapp file opens in the EventFlow editor.

    StreamBase may open some file types in an external editor or application, if the file type you select is associated with that program on your system.

  • Open With

    Opens the selected file using an editor that you specify. A submenu presents a list of options appropriate for the selected file type. The option list might include:

    • Text Editor: the standard Eclipse text editor.

    • System Editor: an editor associated with this file type on your system, if defined.

    • Default Editor: the editor associated with this file type in StreamBase Studio.

    Note

    If you need to open very large text files in StreamBase Studio, such as files that exceed 100 MB, you may need to increase the size of the JVM's memory allocation. See

  • StreamBase

    Available when you select certain StreamBase resources, displays a submenu with one or more commands that are appropriate for that resource. Examples of resources and their StreamBase context submenus include:

    • Project

      Add Default Server Configuration File

      Creates a new server configuration file, with default settings, in your project.

      Refresh Typecheck Environment

      Forces detection and resynchronization of resources in your workspace that are needed for typechecking. This is useful when typechecking does not automatically occur; for example, when you make changes to Java source files.

    • sbapp EventFlow file

      Convert to StreamSQL

      Generates a StreamSQL file with the same functionality as the EventFlow application, and opens the new file in the StreamSQL Editor.

      EventFlow Layout → Extract to Layout file

      Removes layout information from the EventFlow sbapp file and saves it in an associated sblayout file of the same name in the same folder. Updates an existing sblayout file, or creates a new one if none exists. See Using EventFlow Layout Options for details.

      EventFlow Layout → Discard

      Removes layout information from the sbapp file and discards it.

  • Run Feed Simulation

    This command is available in the context menu of a sbfs Feed Simulation file when an application is running. It is greyed out under all other conditions.

  • Stop Feed Simulation

    Available in the context menu of a sbfsFeed Simulation file that is currently running. Stops the currently running feed simulation.

Note

For example, the Properties command opens the Eclipse Properties dialog, which is not the same as the Properties view that opens when you select a component in a StreamBase EventFlow diagram.

Migration Notes:

Differences to note if you are migrating from a StreamBase release earlier than 5.0:

  • The Package Explorer replaces the Project view. The Package Explorer is a standard Eclipse view to which StreamBase adds resources and functionality of its own.

  • Previously, you could use the New → Server Configuration context menu command to create a new StreamBase Server configuration file for a project. This command is no longer available; instead, right-click the project folder and choose StreamBase → Add Default Server Configuration file.

Related Topics

See the WorkBench User Guide for help on standard Eclipse functions in the Package Explorer.

Back to Top ^