2009/7/30 Vidar Ramdal vi...@idium.no:
What is the intended behavior for a servlet that is registered as follows:
* @scr.property name=sling.servlet.extensions value=html
* @scr.property name=sling.servlet.resourceTypes
value=sling/servlet/default
* @scr.property name=sling.servlet.methods
2009/8/4 Vidar Ramdal vi...@idium.no:
2009/7/30 Vidar Ramdal vi...@idium.no:
What is the intended behavior for a servlet that is registered as follows:
* @scr.property name=sling.servlet.extensions value=html
* @scr.property name=sling.servlet.resourceTypes
value=sling/servlet/default
*
Bertrand Delacretaz wrote:
On Tue, Aug 4, 2009 at 9:23 AM, Vidar Ramdalvi...@idium.no wrote:
2009/7/30 Vidar Ramdal vi...@idium.no:
What is the intended behavior for a servlet that is registered as follows:
* @scr.property name=sling.servlet.extensions value=html
...
* @scr.property
On Tue, Aug 4, 2009 at 10:08 AM, Carsten Ziegelercziege...@apache.org wrote:
Bertrand Delacretaz wrote:
...if a servlet is registered with
sling.servlet.extensions = html, it should not process any request
that doesn't have an html extension.
Hmm not sure :) I guess this boils down to the
2009/8/4 Carsten Ziegeler cziege...@apache.org:
Bertrand Delacretaz wrote:
On Tue, Aug 4, 2009 at 10:08 AM, Carsten Ziegelercziege...@apache.org
wrote:
Bertrand Delacretaz wrote:
...if a servlet is registered with
sling.servlet.extensions = html, it should not process any request
that
Alexander Klimetschek wrote:
On Fri, Jul 31, 2009 at 11:06 AM, Vidar Ramdalvi...@idium.no wrote:
No, I used only the old-fashioned Javadoc method, but should that make
a difference?
You are right, it should not make a difference, but the bug could only
be in the QDox based way. With QDox,
On Mon, Aug 3, 2009 at 5:04 PM, Carsten Ziegelercziege...@apache.org wrote:
We follow the DS spec and therefore do not read the annotations at
runtime. They're read by the SCR plugin during build time (again with
QDox)
I thought one of the main reasons for Java annotations was to support
Alexander Klimetschek wrote:
On Mon, Aug 3, 2009 at 5:04 PM, Carsten Ziegelercziege...@apache.org wrote:
We follow the DS spec and therefore do not read the annotations at
runtime. They're read by the SCR plugin during build time (again with
QDox)
I thought one of the main reasons for Java
Hi Vidar,
did you give the Javaannotations a try (@SlingServlet [1]), we currently
only work with those instead of QDox and if I remember right I've seen a
testcomponent with the selectors which worked. The SlingServlet annotation
can be found in the felix scr annotations.
Best regards,
Dominik
On Fri, Jul 31, 2009 at 11:06 AM, Vidar Ramdalvi...@idium.no wrote:
No, I used only the old-fashioned Javadoc method, but should that make
a difference?
You are right, it should not make a difference, but the bug could only
be in the QDox based way. With QDox, the properties are read from the
2009/7/31 Alexander Klimetschek aklim...@day.com:
On Fri, Jul 31, 2009 at 11:06 AM, Vidar Ramdalvi...@idium.no wrote:
Also, I see that if I drop the sling.servlet.extensions property,
the servlet seems to be registered as expected:
* @scr.property name=sling.servlet.extensions value=html
*
On Fri, Jul 31, 2009 at 11:06 AM, Vidar Ramdalvi...@idium.no wrote:
Also, I see that if I drop the sling.servlet.extensions property,
the servlet seems to be registered as expected:
* @scr.property name=sling.servlet.extensions value=html
* @scr.property name=sling.servlet.resourceTypes
What is the intended behavior for a servlet that is registered as follows:
* @scr.property name=sling.servlet.extensions value=html
* @scr.property name=sling.servlet.resourceTypes
value=sling/servlet/default
* @scr.property name=sling.servlet.methods values.0=GET values.1=POST
It seems that
13 matches
Mail list logo
