I had assumed that you have an exporter associated with your resource type, but it seems you do not, and that is the issue.To understand this better, please refer to: https://docs.adobe.com/content/help/en/experience-manager-learn/foundation/development/understand-sling-model-exporter.htmlandhttps:/...

I'm not sure this is actually related to the SPA editor, it could be a number of things.To make this easier for us to debug and help. could you create a simple empty component, maybe in we-retail project, with a sample dialog that does not provide you the desired model.json output, then package that...

This is an interesting topic, I have not implemented a solution for this, but if I did, here are my 2 cents:Some assumptions to start with:1. The JSON structure is the same for every instance of your component that's already authored2. You already use a Sling Model or Use class to get data from JSON...

Are you saying you cannot have seperat cache policy for Akamai and The browser? They HAVE to use the same policy? This seems like a strange limitation...

yes, of course, minutes are acceptable. I think Akamai's is 5 minutes or something close to that.  But that is significantly lower than 30 minutes or an hour. and would allow clients to have much longer TTLs.

Ah ok. Yeah, I agree with you on that. But it's hard to get a client to adopt that. Clients typically want an instantaneous experience and want their content live, as soon as they hit publish. Which is not a bad expectation, if the code and APIs support it without complications. Thanks for the insig...

@Jörg, I am no Akamai expert, but I assume what you mean is that cached pages in Akamai will only be refreshed from origin after the TTL has elapsed, correct? so if you have a long TTL, say an hour, this means there will be at most one hour where there are stale pages?

I ran into the same issue. in order to resolve Tags, they must exists under `/content/cq:tags/your/tag` or `/etc/tags` (legacy).The Page#getTags implementation makes a call to TagManager#getTags which in turn tries to resolve the actual tag resource in the repo. Since you are testing in an AEM conte...

oh, I see it now, it's a little button with a "cog" icon on the top right corner of http://localhost:4502/aem/experience-fragments.html/content/experience-fragments Still my concern remains.. it is not documented.

kautuksahni​ any updated on this? I'd really like to know how I can do this correctly. Thanks!