Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Scout/Overview/Scout application"

m
Line 10: Line 10:
 
* Rich client platforms with a J2EE Backend (Equinox, SWT/Swing)
 
* Rich client platforms with a J2EE Backend (Equinox, SWT/Swing)
  
{{ScoutLink|SDK|name=Scoud SDK}} guides the developer in building Scout based SOA compliant applications.
+
{{ScoutLink|SDK|name=Scout SDK}} guides the developer in building Scout based SOA compliant applications.
  
 
== See also ==
 
== See also ==

Revision as of 04:18, 20 July 2010

The Scout documentation has been moved to https://eclipsescout.github.io/.

An application built with Scout is a complete application. Typically it has a UI with perspectives, views, forms and pages. It may also have a back-end part that is running inside an application server with server-side Equinox.

Examples of such applications are:

  • Standalone rich client platforms (Equinox, SWT/Swing)
  • SOA/ESB node consisting of J2EE with service registry and web services (Equinox)
  • Rich client platforms with a J2EE Backend (Equinox, SWT/Swing)

The Scout documentation has been moved to https://eclipsescout.github.io/. guides the developer in building Scout based SOA compliant applications.

See also

Copyright © Eclipse Foundation, Inc. All Rights Reserved.