Weblets

General Functions

The application of those principles is very easy, all the application programmer has to use, is the frontend specific API .

Weblets tries to stay the same as much as possible in its APIs and their results over all frameworks, so that the application programmer can be sure that the final result stays the same, not depending on the underlying framework being used.

The basic idea of the Weblet fronted API, are two contractual functions/methods.

Code 1: Contract Functions/Methods

    url(<webletname>,<path to resource>)
    resource(<webletname>,<path to resource>)

In every framework supported, you always will find them one way or the other.

The main difference between those two contractual methods is, that url serves up a full url including the current web application context, while resource only serves up the relative path to the resource.

The following code example shows the differences between the two functions.

Code 2: Difference between url and resource in a pseudo API

        url ("org.myapp.html","/myresource.js")
        resolves to /my-webapp/faces/weblets/myapp/myresource.js

        resource( "org.myapp.html","/myresource.js")
        resolves to /faces/weblets/myapp/myresource.js

Contents

1. Users documentation: Index
2. What is new in this release
3. Users documentation: Getting started
4. Users documentation: Setup guide
5. Users documentation: Introduction to the api patterns
6. Users documentation: JSP Weblets usage guide
7. Users documentation: Servlet Weblets usage guide
8. Users documentation: JSF Weblets usage guide
9. Users documentation: Resources Weblets usage guide
10. Users documentation: Weblets packaging guide
11. Users documentation: Weblets Subbundles
12. Users documentation: Weblets reporting guide
13. Developers documentation: Programming Weblets
14. Users documentation: Weblets general FAQ