No able to access file located in /etc/test folder | Community
Skip to main content
snehag07
Level 2
August 4, 2017
Solved

No able to access file located in /etc/test folder

  • August 4, 2017
  • 18 replies
  • 7228 views

Hi,

I am using AEM 6.3 version.

I am trying to access file componentId.jsp located in /etc/test folder from /apps/myWebsite, but I am getting file not found error.

I checked the permissions, it is present.

Could you please suggest?

I was able to do it in AEM 6.2 version.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by smacdonald2008

Yes - it no longer works in 6.3.

18 replies

snehag07
snehag07Author
Level 2
August 10, 2017

I  also tried the same, putting jsp under /apps works.

But can you please suggest on the files in /etc, is there any restriction?

Due to due, we will need to do changes in current implementation.

susheel
Level 5
August 10, 2017

Hi Sneha,

Its better to move out JSP out of etc and place it apps.

Move out and do a search and replace of references.

snehag07
snehag07Author
Level 2
August 10, 2017

Thank you all for your comments.

I will make the changes accordingly.

Can we say that it is a limitation in AEM 6.3?

As i already mentioned, in previous versions i was able to access jsp file from /etc folder

smacdonald2008
smacdonald2008Accepted solution
Level 10
August 10, 2017

Yes - it no longer works in 6.3.

susheel
Level 5
August 10, 2017

I have checked it in 6.3, it doesn't work there as well. Also etc is not right place for jsp's anyhow.

VeenaVikraman
Community Advisor
Community Advisor
August 10, 2017

I agree with susheel and scott. Together you have to keep in mind that ultimately you have to let go off JSPs. It should have been high time you rewrote everything to Touch UI and sightly.

susheel
Level 5
August 10, 2017

I agree with Veena. Its better to move on to sightly rather than working on JSP's anymore.

Sightly(HTL) separates out the back end logics to java or javascript use api and front end is just to read the properties, loop the properties and display it. It looks more clean and manageable.

joerghoh
Adobe Employee
Adobe Employee
January 26, 2018

Hi,

That might be the result of the introduction of a service user into the resource resolving process. In earlier versions the sling script resolver used an admin session, and you were able to include files from the complete repository. Now it is using a service user which can read only on /apps and /libs.  That means that you have to place your rendering scripts (JSP, HTL) in /apps and /libs.

That's for security reasons. And I would not change the permissions of that service user!

Jörg