An update on this. I have managed to get further by stripping out large chunks of the swaggerfile, with only one simple GET operation then AEM accepts the swaggerfile - https://app.swaggerhub.com/apis/pgleghorn/PegaAPI/12.0.4
It seems that AEM does not like the GET paths with parameters, or any PUT/POST operations, from my original swaggerfile. However it is a tricky process through trial and error to find out what specifically is causing the problem. Trace logger on error.log didn't yield any new info.
I am getting same issues in AEM forms 6.3 while creating form data model.
Can any one help me in this.
Hi Phil and Venkat,
NPE is occurring due to missing of properties in Content model definitions (line no. 825) in Pega API Swagger.
I have logged bug in product for fixing this use case and for now there is workaround.
- Open the swagger file
- Find Content definition (available at line no 825 in yaml file)
- add dummy property in content
Upload the updated swagger and FDM editor should be showing all the models and services
Vijay Kumar J