Level 9

Solved

AEM 6.4 upgrade @reference does not work in a workflow

16 replies
7942 views
Translate All

All i have a workflow process step and it references class A that exposes a service, but when i check for the value of A in the process step, it appears to be null,

i am injecting this service A using the @Reference.

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

N

NitroHazeDevAccepted solution

Level 9

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 scr annotation errors and components appear to be in satisfied state

Infact abstract keyword for a service at times sets the component to state "16", solution - remove abstract keyword

If you have nested inheritance and a class that is abstract and implement workflowprocess, keep it simple, take off abstract keyword and avoid inheritance since if a child class(extending parent class that implements workflow process) is invoked the annotations of the parent class is null, so just keep child class that implements workflowprocess and avoid inheritance where the parent class uses annotation and no abstract keyword.

https://forums.adobe.com/thread/2461255

Show previous replies

arunpatidar

Community Advisor

Hi,

*you missed @Component annotation in your service implementation.

below is correct code:you can try with this

package com.test.core.workflows.general;
import org.osgi.service.component.annotations.Component;

import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
@Component
public class DemoWFServiceImpl implements DemoWFService {
protected final Logger log = LoggerFactory.getLogger(this.getClass());

String PrefixMessage = "Service Invoked by Workflow -- ";

@Override
public String showMessage(String msg) {
return PrefixMessage + msg;
}
}

Translate

Arun Patidar

N

NitroHazeDevAuthor

Level 9

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 step

reasons:

1. Class that implements workflow process is marked abstract

Yet to investigate, ..

This worked smooth on 6.2..

Translate

smacdonald2008

Level 10

Please watch the video - i show all the code and shows it works in 6.4

Translate

N

NitroHazeDevAuthor

Level 9

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

Translate

smacdonald2008

Level 10

In my example - i did not use that. Simply used an interface and the implementation class that uses @Component.

Let me know if you find a solution when that keyword is used (which seems to be causing an issue).

Translate

N

NitroHazeDevAuthorAccepted solution

Level 9

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 scr annotation errors and components appear to be in satisfied state

Infact abstract keyword for a service at times sets the component to state "16", solution - remove abstract keyword

If you have nested inheritance and a class that is abstract and implement workflowprocess, keep it simple, take off abstract keyword and avoid inheritance since if a child class(extending parent class that implements workflow process) is invoked the annotations of the parent class is null, so just keep child class that implements workflowprocess and avoid inheritance where the parent class uses annotation and no abstract keyword.

https://forums.adobe.com/thread/2461255

Translate

Sign up

Login with SSO

Login to the community

Login with SSO