Difference between revisions of "Scout/Overview/Scout application"
m (Scout application moved to Scout/Overview/Scout application) |
|||
| (One intermediate revision by one other user not shown) | |||
| 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= | + | {{ScoutLink|SDK|name=Scout SDK}} guides the developer in building Scout based SOA compliant applications. |
== See also == | == See also == | ||
| − | * {{ScoutLink|Tutorial| | + | * {{ScoutLink|Tutorial|name=Scout Tutorials}} |
| − | + | ||
| − | + | ||
Latest revision as of 09:04, 2 May 2012
| Scout |
| Wiki Home |
| Website |
| Download • Git |
| Community |
| Forums • Blog • Twitter • G+ |
| Bugzilla |
| Bugzilla |
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)
Scout SDK guides the developer in building Scout based SOA compliant applications.