Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

tims19814439
tims19814439
Offline

Badges

Badges
5

Accepted Solutions

Accepted Solutions
0

Likes Received

Likes Received
0

Posts

Posts
9

Discussions

Discussions
6

Questions

Questions
3

Ideas

Ideas
0

Blog Posts

Blog Posts
0
Top badges earned by tims19814439
Customize the badges you want to showcase on your profile
Re: Sling servlet txt extension not working with OSGi DS 1.2 annotations - Adobe Experience Manager 04-01-2019
This actually works. Does this mean that all requests to the page node are internally redirected to _jcr_content for HTML and XML calls but not for other extensions ?

Views

4.8K

Likes

0

Replies

3
Re: Sling servlet txt extension not working with OSGi DS 1.2 annotations - Adobe Experience Manager 03-01-2019
Thanks for your answer Arun Patidar​. At this point I don't really want to switch the whole interface to a sling filter so I will just map to .xml and rewrite from .txt to .xml in apache. Thanks for your help everyone!

Views

3.0K

Likes

0

Replies

6
Re: Sling servlet txt extension not working with OSGi DS 1.2 annotations - Adobe Experience Manager 03-01-2019
thanks for the tip I will change the resource type to the short one

Views

3.0K

Likes

0

Replies

8
Re: Sling servlet txt extension not working with OSGi DS 1.2 annotations - Adobe Experience Manager 03-01-2019
I'm actually using the OSGI component annotation the felix annotations are not available in the 6.2 architype I'm using

Views

3.0K

Likes

0

Replies

10
Re: Sling servlet txt extension not working with OSGi DS 1.2 annotations - Adobe Experience Manager 03-01-2019
This unfortunately just makes it possible for the default GET servlet to handle the request. However I would like my own servlet to handle the request.

Views

3.0K

Likes

0

Replies

0
Sling servlet txt extension not working with OSGi DS 1.2 annotations - Adobe Experience Manager 02-01-2019
I am trying to create a servlet to serve a robots.txt. The servlet to handle this request is mapped on the website page resource and looks like this:When I visit the page like this "/content/website.robots.txt" I am presented with an 404 error and the get of the servlet is never called. When I change "sling.servlet.extensions" to xml and visit "/content/website.robots.xml" the get gets called and the servlet works.I am using AEM 6.2 with OSGI 6.0.0Is it impossible to map to .txt as extension or ...

Views

3.7K

Likes

0

Replies

14
Re: restricting cq:dialog options on included child components - Adobe Experience Manager 13-08-2018
when you say 1 on 1 approach how would you suggest doing this efficiently with as little duplication as possible ? for this instance with a title component

Views

856

Likes

0

Replies

0
Re: restricting cq:dialog options on included child components - Adobe Experience Manager 13-08-2018
this would also mean that I have multiple title components which do nothing but restrict the cq dialog options and would in my opinion also create complexity

Views

864

Likes

0

Replies

0
restricting cq:dialog options on included child components - Adobe Experience Manager 13-08-2018
I have a composite component consisting of three included components an image a title and a text component. Normally since the title component inherits the `wcm/foundation/components/title` the data-sly-resource included component gets the title type option (h1,h2...) from it's parent. However for this specific composite component I want to limit the type option to just have h2 available. The Title component is included in the composite component like this: This allows the content editor to edit...

Views

1.9K

Likes

0

Replies

7