Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

Dave_Hughes
Dave_Hughes
Offline

Badges

Badges
19

Accepted Solutions

Accepted Solutions
7

Likes Received

Likes Received
6

Posts

Posts
83

Discussions

Discussions
4

Questions

Questions
79

Ideas

Ideas
0

Blog Posts

Blog Posts
0
Top badges earned by Dave_Hughes
Customize the badges you want to showcase on your profile
Re: Client code for cq:layout=auto - Adobe Experience Manager 28-05-2016
Thank you, Scott.  That's unfortunate, but it's an answer.

Views

448

Likes

0

Replies

0
Re: Client code for cq:layout=auto - Adobe Experience Manager 27-05-2016
Thanks Scott. Do you know what the turn around time is for this type of request?

Views

437

Likes

0

Replies

0
Re: Client code for cq:layout=auto - Adobe Experience Manager 27-05-2016
Thanks, but I am familiar with setting the cq:layout to editbar. My question is specifically about setting the layout to auto. The documentation describes auto as "The choice is left to the client side code". I interpret this as meaning that the choice between editbar and rollover is made at page render time, determined by some client code (JSP/JavaScript/something else?). I am looking for an example or documentation for the "client code" that would dictate which layout to use.EDIT: you beat me ...

Views

446

Likes

0

Replies

0
Client code for cq:layout=auto - Adobe Experience Manager 27-05-2016
I would like to use cq:layout="auto" in my component's edit config. https://docs.adobe.com/docs/en/cq/5-5/developing/components/edit_config.html#cq:layoutThe documentation states that auto allows the client code to determine if it should be editbar or rollover, but I can't find any documentation or literature on how to achieve this. Could anybody provide sample code or links to help? Thanks!

Views

913

Like

1

Replies

9
Submitting a message to the AEM 5.6.1 Inbox (graceful workflow process step failure) - Adobe Experience Manager 04-04-2016
Hello,We have implemented a custom workflow process step to perform an operation against an integration. The particulars aren't important.Currently, if an error occurs when we call the integration, we throw a workflow exception. This causes the step to be retried (10 attempts), after which the workflow is halted and a the exception is sent to the AEM inbox (/inbox) as a FailureItem.We wish to change this behaviour so that the process step is tried only once. We wish to make it a graceful failure...

Views

1.6K

Likes

0

Replies

2
Re: Dispatching a request from a workflow process (5.6.1) - Adobe Experience Manager 24-02-2016
Thank you again, Kunal. I had already searched for the source of SlingRequestProcessorImpl for setStatus, and found none; I did, however, overlook the calls to sendError, which I suppose my wrapper also needs to implement, in order to set status code. Once again, thank you.

Views

647

Likes

0

Replies

0
Re: Dispatching a request from a workflow process (5.6.1) - Adobe Experience Manager 24-02-2016
kunal23 wrote... I guess you used the RequestResponseFactory service to get the dummy request, response objects for sending a request to the SlingRequestProcessor. The request, response objects this service creates are just mock objects and they do not have any implementation of setStatus and getStatus methods. To get the status of the response you can create your own response class implementing the HTTPServletResponse interface. In the setStatus method you can set the value passed in the method...

Views

595

Likes

0

Replies

0
Re: Dispatching a request from a workflow process (5.6.1) - Adobe Experience Manager 24-02-2016
Another excellent response, thank you so much.

Views

591

Likes

0

Replies

0
Re: Create Page Option appears to be null and not available in AEM - Adobe Experience Manager 24-02-2016
Happy to help. I've seen several other individuals trip over this before as well. I'm not sure how it is that the problem is so common, as it seems to require that a user delete/renames a node that they should not, but it does seem to happen alarmingly frequently. I'd love to see Adobe make the Projects and Site Admin interfaces more durable, so they don't just fail silently under these conditions.

Views

2.5K

Likes

0

Replies

0