Hi, my two cents just in case you are not aware of this feature:
With any Servlet >= 3.0 compatible container, anything in a META-INF/resources directory in a JAR in WEB-INF/lib is automatically exposed as a static resource.
Not sure how this could be applied in the current setup of Stanbol. But if this also works somehow in OSGi, definitely a pretty nice way to solve this issue.
Best, Sergio On 30/11/12 10:43, Reto Bachmann-Gmür wrote:
Hello At Apacheconeu I've been talking with Rupert and others on how static resources should be handles. We agreed that they should no longer need to be referenced in the webfragment. I was in favour of just having a fixed location in the jar but Rupert convinced me that this default location should be overwritable with a value in the MANIFEST.MF file. In the long term it should be possible to have file-backed resources at any location in the URI space but as a first step only the architecture for the resources below "/static/" shall be changed. E.g: MANIFEST.MF Stanbol-Static: /META-INF/stanbol-static The jar contains /META-INF/stanbol-static/static/hello.txt Stanbol will serve that file at http://<host>/static/hello.txt if the jar contains /META-INF/stanbol-static/hello.txt this will for now generate a warning that currently the files must be in a subfolder called "static" to be served (in future it should be served at http://<host>/hello.txt). Any thoughts? Any volunteers? Cheers, Reto
-- Sergio Fernández Salzburg Research +43 662 2288 318 Jakob-Haringer Strasse 5/II A-5020 Salzburg (Austria) http://www.salzburgresearch.at
