Expand my Community achievements bar.

Attention Community Users: The AEM Forms community is now read-only temporarily due to a spam attack.
SOLVED

Remote debug post.POST.jsp

Avatar

Former Community Member

Using AEM 6.2 SP1.

We are using VLT to integrate/synch Eclipse and JCR.

This *should* also allow us to remote debug JSPs,but it doesn't seem to allow us to remote debug post.POST.jsp.

Suggestions?

I am using this: https://helpx.adobe.com/experience-manager/using/creating-aem-project-using-eclipse.html as a starting point.

-Joel

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Solved it. Used -debug [port] when starting the quickstart. I was using the traditional JVM debug approach, which opens a port on the launcher, no the actual AEM VM

View solution in original post

1 Reply

Avatar

Correct answer by
Former Community Member

Solved it. Used -debug [port] when starting the quickstart. I was using the traditional JVM debug approach, which opens a port on the launcher, no the actual AEM VM

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----