Dave Tolls wrote:I expect there's something in the docs.
I'm not too sure why it thought it ought to create a mapping table.
Actually, thinking about it, isn't this actually a many to many?
If a single Filter (in the form of a FilterGroup) can map to many Filters, those Filters are (by their nature) mapped in reverse to the original Filter.
In fact, looking at your model, I think your model is not quite right.
If a FilterGroup is a collection of Filters, then why are you extending Filter?
That seems to me to be the base of the problem.
It may be correct, but it looks a bit odd to me.
Dave Tolls wrote:I assume its based around this:
That would result in a Filter referencing multiple other filters.
Dave Tolls wrote:Can you explain what your issue is?
Those screenshots don't really help.
eugene malcolumn wrote:
![]()
Stephan van Hulst wrote:I'm sorry, I can't understand what you wrote. Please be more clear in what you're trying to do and what the problem is.
Stephan van Hulst wrote:
eugene malcolumn wrote:wanted to create a java client only.
Okay, so what's stopping you? If you know whether the response is going to be in JSON or XML or something you can use the appropriate parser, then look for the _links property and display them in a component that handles navigation for you.
Stephan van Hulst wrote:Well, it depends on the format in which your REST API sends its responses. For instance, if you follow the quick start here, you will get a response from the server similar to:
You can create a very simple JavaScript client that displays the content, and adds a navigation bar that contains a home button that links to the root page, a refresh button that links to the "self" url, and additional buttons for any other links that may appear in the "_links" property.
Stephan van Hulst wrote:Please make your question a little bit clearer.
There's no such thing as "a hateos". It's HATEOAS and it's an abstract concept and not "something you can call".
What link do you want to get? From where?