As a reference, the following ICEfaces 1.8 components are using dynamic resource API:
1. OutputResource:
Uses it to server various types of resources. Since there is a callback API for this ultimately the scoping decision should belong to the application for each resource.
2. DataExporter:
Uses a FileResource to server generated report. (Application control).
3. HtmlGraphicImage:
Uses a ByteArrayResource to support byte array to generate an image. (Application control)
4. InputRichText:
Using various Resource utilities(e.g.)
- JarResource: to server custom JS from jar
- ResourceLinker to serve resources of zip from the jar.
( These are under component control, and should probably be Application scope. )
As a reference, the following ICEfaces 1.8 components are using dynamic resource API:
1. OutputResource:
Uses it to server various types of resources. Since there is a callback API for this ultimately the scoping decision should belong to the application for each resource.
2. DataExporter:
Uses a FileResource to server generated report. (Application control).
3. HtmlGraphicImage:
Uses a ByteArrayResource to support byte array to generate an image. (Application control)
4. InputRichText:
Using various Resource utilities(e.g.)
( These are under component control, and should probably be Application scope. )