Expand my Community achievements bar.

Enhance your AEM Assets & Boost Your Development: [AEM Gems | June 19, 2024] Improving the Developer Experience with New APIs and Events
SOLVED

HTL Template on Publisher throws error "Arguments cannot be null"

Avatar

Level 2

Does anyone know why a HTL template would be working fine on Author but on Publisher it throws the error "Arguments cannot be null"? The publisher has no issues running JSP templates.

Is there any way that I can get a bit more information i.e. a Publisher error log?

Edit 1: I have further narrowed this down to the inclusion of a Java file in my template component. The file can be empty and it still throws the error.

1 Accepted Solution

Avatar

Correct answer by
Level 2

I actually solved this just before going away for the weekend. The issue was that I was referencing the class directly (data-sly-use.headjava="Head") and instead had to include the package (data-sly-use.headjava="apps.site.components.page2017.global.head.Head").

I am unsure at this point as to why I need this reference on Publisher and not on Author, do you know what would be missing on the Publisher to cause this?

Also, as I said in my original question "Is there any way that I can get a bit more information i.e. a Publisher error log?". I need this in order to both help me narrow down the cause of issues and provide a stacktrace if requested.

EDIT 1: I now have access to the error logs, so my question about this has been solved.

View solution in original post

2 Replies

Avatar

Employee

Can you share your code and stacktrace, that will provide mode info to us.

Avatar

Correct answer by
Level 2

I actually solved this just before going away for the weekend. The issue was that I was referencing the class directly (data-sly-use.headjava="Head") and instead had to include the package (data-sly-use.headjava="apps.site.components.page2017.global.head.Head").

I am unsure at this point as to why I need this reference on Publisher and not on Author, do you know what would be missing on the Publisher to cause this?

Also, as I said in my original question "Is there any way that I can get a bit more information i.e. a Publisher error log?". I need this in order to both help me narrow down the cause of issues and provide a stacktrace if requested.

EDIT 1: I now have access to the error logs, so my question about this has been solved.