Application resource requests passed to URIHandler

[Marko Gronroos]

If I have a class resource (or some other application resource type), there will be a request for an APP/ object. This is passed to URIHandler of Application. It can be handled somewhat easily, but may be very unexpected and it would probably be best to handle it before the URIHandler.

Below is a workaround:

   public DownloadStream handleURI(URL context, String relativeUri) {
        if (relativeUri.startsWith("APP"))
            return super.handleURI(context, relativeUri);

[Jani Laakso]

I'd keep it this simple, developer might want to do some processing for class resources and this is the way to do it.

Unless, there already is a better way to handle these?

We could of course make our API better by adding handleResourceURI which typically developers would not override but I would not enlarge our API for now.

[Jani Laakso]

Yes, Toolkit Resource objects should not fall down for handleURI.

If someone wishes to handle resources dynamically they should override handleURI and use own "proprietary" means without use of Toolkit Resource objects because these resources are mapped to special reserved URI */APP/*.

Another solution would be to extend Toolkit resource class and add custom resource handling stream code there..

[Jani Laakso]

Ahh, this is but a documentation issue. You should not extend Application, you should do this instead:

 public void init() {

        final Window main = new Window("Hello window");
        setMainWindow(main);

        URIHandler uriHandler = new URIHandler() {
            public DownloadStream handleURI(URL context, String relativeUri) {
                System.out.println("handleURI=" + relativeUri);
                // TODO Auto-generated method stub
                return null;
            }
        };
        main.addURIHandler(uriHandler);

    }

Above code does not receive calls from Toolkit resources, they are handled earlier.

If you do extend Application and override handleURI method then you should understand that your custom application is responsible of handling of Toolkit resources aswell (such as APP resources, native window resources).

Add this to documentation..

[Jani Laakso]

The reason why handleURI method is public is because ApplicationServlet? requires it.

[Joonas Lehtinen]

Milestone Sprint 4 backlog deleted

[Joonas Lehtinen]

Milestone User Interface Library 5.1.2 deleted

[Matti Tahvonen]

in [4528] to Application.handleUri() javadocs. Magi, it is up to you to consider if the case needs something into manual also.

[Marko Gronroos]

Some documentation in [4530], may need some further work, the example is a bit limited.