Hi
Am 20.12.2011 um 16:22 schrieb sam ”:
sling.servlet.paths = /imgs only registers the servlet for:
GET /imgs
The servlet should be registered for:
GET /imgs/blah/blah.jpg, too.
It would also be for
GET /imgs.ext/blah/blah/blah.jpg
where /blah/blah/blah.jpg would be the request
Do not complicate things.
Do not change urls.
Use repository path as is (with very minimum url rewrite.. such as
/foo/bar to /content/foobar.com/foo/bar).
For dynamic resources (resources that do not exist), use something other
than Sling.
I solved my problem by implementing it in php.
On
U... OK. Sling's ResourceProviders provide a way to create
synthetic resources for an entire sub-tree.
But if you want to use PHP, that's up to you.
Justin
On Tue, Dec 20, 2011 at 12:51 PM, sam ” skyn...@gmail.com wrote:
Do not complicate things.
Do not change urls.
Use repository path
Could a SlingOptingServlet be adapted for this purpose?
On Dec 20, 2011, at 10:37 AM, Felix Meschberger fmesc...@adobe.com wrote:
Hi
Am 20.12.2011 um 16:22 schrieb sam ”:
sling.servlet.paths = /imgs only registers the servlet for:
GET /imgs
The servlet should be registered for:
ResourceProvider implementation seems to be what I need.
@Component
@Service
@Properties({
@Property(name = ResourceProvider.ROOTS, value={/imgs})
})
public class SyntheticResourceProvider implements ResourceProvider {
@Override
public Resource getResource(ResourceResolver
Hi,
Am 20.12.2011 um 19:18 schrieb Colin Flanagan:
Could a SlingOptingServlet be adapted for this purpose?
No, because this only comes into play, when canidate servlets and scripts have
already been selected by the ServletResolver. And the servlet configuration
setup comes nto play when
Hey,
In repository, there is no resource /imgs.
And, I want to register a servlet in osgi bundle that will handle all
requests to /imgs/*
For example,
GET /imgs/some/image.jpg
GET /imgs/foo/bar.tags.xml
GET /imgs.json
GET /imgs.xml
GET /imgs/foo/bar.html
and POST..
I tried:
@Property(name =
On 19.12.11 23:35, Alexander Klimetschek aklim...@adobe.com wrote:
Also, you could put it under /content/imgs or /libs/imgs
Ups, I meant /apps/imgs or maybe /etc/imgs (/apps /libs should usually
be closed as much as possible for public instances to avoid any chance of
exposing code or
