I was surprised .. and i knew editing permissions for sling scripting giving permissions to code under apps is not the right way , thanks to people to pointed out against it....So apparently in 6.2 sling scripting user with certain privileges were used to access classes that extend wcmuspojo, i rais...

Hi,I had to alter the code discussing with AdobeTry this:Class extending WCMUsepojo----------------GetResourceResolverService getService = getSlingScriptHelper().getService(GetResourceResolverService.class);if(getService ==null)return;resourceResolver= getService.getServiceResourceResolver("core-adm...

So Scott, i finally have a response and after consultation and weeks of debugging assuming i was doing something wrong for something that is so simple,​ i am asked (by adobe) to avoid using @reference in abstract classes , and this worked on 6.2 and is something that breaks in 6.4, , with bunch of s...

Yes Scott, that helps, but with the keyword abstract there are issues , so looking into it

Thanks Arun, i had that in my workflow, but missed adding it here ..so here are the updates:I got a custom workflow to work but the one i was trying didn't work and would not appear in the dropdown in the custom process stepreasons:1. Class that implements workflow process is marked abstractYet to i...

Sure.. no problem at all

Sure thanks i believe i used maven arch 13, but i am attaching the code herepackage com.test.core.workflows.general;public interface DemoWFService {public String showMessage(String msg);}------------------------------------package com.test.core.workflows.general;import org.slf4j.Logger;import org.sl...

Will be logging a ticket with Adobe,Created classes as you've shared and weird issues were noted1. With @reference annotation, custom workflow process  (java)step did not appear in the dropdown  for the workflow2.Without @Reference annotation, the process step java class was visible.

So i logged a day care ticket(#152132) and Adobe mentioned its a bug/known issue, SLING-7525 missing content-headers, they mentioned the response header is missing Content-Type,Binary Provider Overlay servlet as workaround was suggested but it didn't help.So suggestions provided by adobe:- Upload PN...

It looks like a bug in 6.4 , here are the suggestions i have received from adobe,since 6.4 rendered svg assets with OOTB image component(drag drop image to the component), mockup your component to do what image component does, or use png, i used the png/jpeg from the renditions folder