Issue in sightly component after upgrade from 6.0 to 6.2 | Community
Skip to main content
diptinarang
Level 3
March 22, 2017
Solved

Issue in sightly component after upgrade from 6.0 to 6.2

  • March 22, 2017
  • 9 replies
  • 4477 views

We are experiencing issues in sightly components, wherever we have referenced Java classes like this - "global.Packages.com.xyz.wcm.utils.ABCClient"

 

Exception:

GET /content/xyz/ab/new.html HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl service: Uncaught SlingException

java.lang.NoClassDefFoundError: Could not initialize class com.xyz.wcm.utils.ABCClient

    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

    at java.lang.reflect.Method.invoke(Method.java:498)

    at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:126)

    at org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:225)

    

 

I couldn't find any deprecations related to this in following documents:

https://docs.adobe.com/docs/en/aem/6-2/develop/ref/javadoc/deprecated-list.html#package

https://docs.adobe.com/docs/en/aem/6-2/release-notes/deprecated-removed-features.html

https://docs.adobe.com/docs/en/aem/6-2/develop/ref/diff-previous/changes.html

 

Also the fix mentioned here, didn't work:

http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manager.topic.html/forum__ulkn-we_are_experiencing.html

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 diptinarang

The issue is resolved by granting admin like rights to system user. But the error message thrown was bit misleading and that's why I suspected that issue is in sightly.

Thanks everyone for your valuable inputs.

9 replies

daniel_henriqu1
Level 4
March 22, 2017

Hi, Dipti.

To which classes/packages are you referring to? Are they part of the AEM core or are they custom/3rd-party?

What is the status of the bundle that export those packages/classes? Is it active?

Regards,

Daniel.

diptinarang
Level 3
March 22, 2017

Thanks for reverting Daniel. These are our custom classes and they are working fine when referenced in JSP or other Java code.

I checked the status of bundle which export this class and it is active.

Thanks, Dipti

joerghoh
Adobe Employee
Adobe Employee
March 22, 2017

Hi,

what is this class "ABCClient" specifically? Is it a WCMUse Pojo, a SlingModel? Or just a random class which is referenced from your Javascript (?) models?

Jörg

diptinarang
Level 3
March 23, 2017

Jörg Hoh wrote...

Hi,

what is this class "ABCClient" specifically? Is it a WCMUse Pojo, a SlingModel? Or just a random class which is referenced from your Javascript (?) models?

Jörg

 

It's a random class.

Thanks, Dipti

joerghoh
Adobe Employee
Adobe Employee
March 23, 2017

Hi Dipti,

does this happen only for some classes or for all? In any way I recommend you to open a ticket at Adobe support.

Jörg

diptinarang
Level 3
March 23, 2017

It is happening for all classes. 

Feike_Visser1
Adobe Employee
Adobe Employee
March 23, 2017

Can you also try to test this on a vanilla 6.2 instance?

diptinarang
diptinarangAuthorAccepted solution
Level 3
March 23, 2017

The issue is resolved by granting admin like rights to system user. But the error message thrown was bit misleading and that's why I suspected that issue is in sightly.

Thanks everyone for your valuable inputs.

Feike_Visser1
Adobe Employee
Adobe Employee
March 23, 2017

You mean on the OS?, since 6.2/6.1 the compiled files are saved on the OS.