View Code? Open in Web Editor
NEW
This project provides webservices against the Hippo CMS content repository
Home Page: https://github.com/jreijn/hippo-addon-restful-webservices/wiki
License: Apache License 2.0
hippo-addon-restful-webservices's Introduction
Welcome to my little spot on GitHub!
๐ญ Iโm currently working on Java, Serverless and Containers on AWS .
๐ฑ Iโm currently learning Kotlin, GraalVM and TypeScript .
๐ฏ Iโm looking to collaborate on helping Java devs adopt the serverless mindset .
๐ฌ Ask me about Java, Spring and AWS!
๐จโ๐ป Read more about my thoughts and learnings @ www.jeroenreijn.com
๐ซ How to reach me: @jreijn
hippo-addon-restful-webservices's People
Contributors
Stargazers
hippo-addon-restful-webservices's Issues
It seem that the JSON API format is quite nice when it comes to defining a payload for JSON REST services. It might be an idea to change the existing endpoints and move towards this format.
http://jsonapi.org/format/
From a usage perspective it would be nice to have query api, so you can find nodes from the repository.
java.lang.NoClassDefFoundError: Lorg/apache/jackrabbit/core/stats/RepositoryStatisticsImpl
It looks like an incompatible Jackrabbit Version (Hippo CMS makes use of 10.1, this solutions uses older one)
It would be nice to manage the users through the REST API. Therefor we need basic CRUD operations on a user.
We need a content based API endpoint. It does not have to be as generic as the HST does, but it should support CRUD operations on document in a non JCR / Node way.
For ease of deployment it would be nice if there is a war deployable, so there is no web.xml customization needed.
Right now you can specify an offset and limit. It would be nice if the query result would provide next / prev links to navigate the resultset.
We need an endpoint for images. Ideally this needs to work with POST and the workflow API, so that image scaling happens in the correct way.
I think it better to remove the versioning from the API endpoints.