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
Community profile tims19814439 Level 2
Job title here
Location here
5 BADGES
Level 2

Level 2

Learn more
Joined the community 05-01-2018 1:18:43 AM
Offline
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
Avatar
Give Back 5
Level 2
tims19814439
Level 2

Likes

0 likes

Total Posts

9 posts

Correct reply

0 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Ignite 1
Validate 1
View profile
tims19814439
- Adobe Experience Manager
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.5K

Likes

0

Replies

3
Re: Sling servlet txt extension not working with OSGi DS 1.2 annotations
Avatar
Give Back 5
Level 2
tims19814439
Level 2

Likes

0 likes

Total Posts

9 posts

Correct reply

0 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Ignite 1
Validate 1
View profile
tims19814439
- Adobe Experience Manager
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

2.6K

Likes

0

Replies

6
Re: Sling servlet txt extension not working with OSGi DS 1.2 annotations
Avatar
Give Back 5
Level 2
tims19814439
Level 2

Likes

0 likes

Total Posts

9 posts

Correct reply

0 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Ignite 1
Validate 1
View profile
tims19814439
- Adobe Experience Manager
thanks for the tip I will change the resource type to the short one

Views

2.6K

Likes

0

Replies

8
Re: Sling servlet txt extension not working with OSGi DS 1.2 annotations
Avatar
Give Back 5
Level 2
tims19814439
Level 2

Likes

0 likes

Total Posts

9 posts

Correct reply

0 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Ignite 1
Validate 1
View profile
tims19814439
- Adobe Experience Manager
I'm actually using the OSGI component annotation the felix annotations are not available in the 6.2 architype I'm using

Views

2.6K

Likes

0

Replies

10
Re: Sling servlet txt extension not working with OSGi DS 1.2 annotations
Avatar
Give Back 5
Level 2
tims19814439
Level 2

Likes

0 likes

Total Posts

9 posts

Correct reply

0 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Ignite 1
Validate 1
View profile
tims19814439
- Adobe Experience Manager
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

2.6K

Likes

0

Replies

0
Sling servlet txt extension not working with OSGi DS 1.2 annotations
Avatar
Give Back 5
Level 2
tims19814439
Level 2

Likes

0 likes

Total Posts

9 posts

Correct reply

0 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Ignite 1
Validate 1
View profile
tims19814439
- Adobe Experience Manager
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.4K

Likes

0

Replies

14
Re: restricting cq:dialog options on included child components
Avatar
Give Back 5
Level 2
tims19814439
Level 2

Likes

0 likes

Total Posts

9 posts

Correct reply

0 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Ignite 1
Validate 1
View profile
tims19814439
- Adobe Experience Manager
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

656

Likes

0

Replies

0
Re: restricting cq:dialog options on included child components
Avatar
Give Back 5
Level 2
tims19814439
Level 2

Likes

0 likes

Total Posts

9 posts

Correct reply

0 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Ignite 1
Validate 1
View profile
tims19814439
- Adobe Experience Manager
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

664

Likes

0

Replies

0
restricting cq:dialog options on included child components
Avatar
Give Back 5
Level 2
tims19814439
Level 2

Likes

0 likes

Total Posts

9 posts

Correct reply

0 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Ignite 1
Validate 1
View profile
tims19814439
- Adobe Experience Manager
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.7K

Likes

0

Replies

7