내 커뮤니티 업적 표시줄을 확대합니다.

Submissions are now open for the 2026 Adobe Experience Maker Awards.

Mark Solution

활동이 없어 이 대화는 잠겼습니다. 새 게시물을 작성해 주세요.

해결됨

ACS ErrorPageHandlerService can't be resolved

Avatar

이전 커뮤니티 멤버

I'm trying to use the ACS ErrorPageHandlerService [1] and it has successfully worked in the past (AEM 6.0 SP1). I just build some (totally unrelated) simple code and now the error pages don't work anymore, see error below: 

30.12.2014 12:50:10.005 *ERROR* [0:0:0:0:0:0:0:1 [1419972610002] GET /favicon.ico HTTP/1.1] org.apache.sling.servlets.resolver.internal.SlingServletResolver Calling the error handler resulted in an error java.lang.Error: Unresolved compilation problems: Only a type can be imported. com.adobe.acs.commons.errorpagehandler.ErrorPageHandlerService resolves to a package ErrorPageHandlerService cannot be resolved to a type ErrorPageHandlerService cannot be resolved to a type

In the system console (/system/console/bundles) I can see that the bundle is active and the ErrorPageHandlerService even shows up in the list of services (/system/console/services). Why would it not be resolvable?

 

[1] http://adobe-consulting-services.github.io/acs-aem-commons/

 

PS: I tried to search the forums but it seems it's always under construction or something or at least the search shows me a blank page in 90% of cases...

1 채택된 해결책 개

Avatar

정확한 답변 작성자:
Level 5

paro22 wrote...

I'm trying to use the ACS ErrorPageHandlerService [1] and it has successfully worked in the past (AEM 6.0 SP1). I just build some (totally unrelated) simple code and now the error pages don't work anymore, see error below: 

  1. 30.12.2014 12:50:10.005 *ERROR* [0:0:0:0:0:0:0:1 [1419972610002] GET /favicon.ico HTTP/1.1] org.apache.sling.servlets.resolver.internal.SlingServletResolver Calling the error handler resulted in an error
  2. java.lang.Error: Unresolved compilation problems:
  3. Only a type can be imported. com.adobe.acs.commons.errorpagehandler.ErrorPageHandlerService resolves to a package
  4. ErrorPageHandlerService cannot be resolved to a type
  5. ErrorPageHandlerService cannot be resolved to a type

In the system console (/system/console/bundles) I can see that the bundle is active and the ErrorPageHandlerService even shows up in the list of services (/system/console/services). Why would it not be resolvable?

 

[1] http://adobe-consulting-services.github.io/acs-aem-commons/

 

PS: I tried to search the forums but it seems it's always under construction or something or at least the search shows me a blank page in 90% of cases...

 

I also had same type of issue for the query builder tool, once i downloaded it. But after few days when i downloaded the new package it started work fine. Not sure might be it can the due the enhancement process.

원본 게시물의 솔루션 보기

3 답변 개

Avatar

Employee

what version have you installed of acs-aem-commons?

Avatar

정확한 답변 작성자:
Level 5

paro22 wrote...

I'm trying to use the ACS ErrorPageHandlerService [1] and it has successfully worked in the past (AEM 6.0 SP1). I just build some (totally unrelated) simple code and now the error pages don't work anymore, see error below: 

  1. 30.12.2014 12:50:10.005 *ERROR* [0:0:0:0:0:0:0:1 [1419972610002] GET /favicon.ico HTTP/1.1] org.apache.sling.servlets.resolver.internal.SlingServletResolver Calling the error handler resulted in an error
  2. java.lang.Error: Unresolved compilation problems:
  3. Only a type can be imported. com.adobe.acs.commons.errorpagehandler.ErrorPageHandlerService resolves to a package
  4. ErrorPageHandlerService cannot be resolved to a type
  5. ErrorPageHandlerService cannot be resolved to a type

In the system console (/system/console/bundles) I can see that the bundle is active and the ErrorPageHandlerService even shows up in the list of services (/system/console/services). Why would it not be resolvable?

 

[1] http://adobe-consulting-services.github.io/acs-aem-commons/

 

PS: I tried to search the forums but it seems it's always under construction or something or at least the search shows me a blank page in 90% of cases...

 

I also had same type of issue for the query builder tool, once i downloaded it. But after few days when i downloaded the new package it started work fine. Not sure might be it can the due the enhancement process.

Avatar

이전 커뮤니티 멤버

It was version 1.8.0. Oddly enough it works now with 1.9.2 after removing the acs-commons folder under apps, removing our clients apps folder as well as the sling folder...

Now I'm just trying to understand the OSGi logic of this I guess, like why would it show this error if the bundle is active and the service does exist?