Remo

I will keep the ticket open to clean up the area a bit to make it more robust. Probably best by moving away from basic strings.

what is the original exception? it would make sense to adjust crnk-core to give a 4xx error. Maybe a BadRequestException would be most suitable in case of an ID parsing...

Yes, true. So far the top-level fields are hold as meta-model within ResourceInformation and ResourceField. There is so far no concept of nested/complex types as attributes. In general I think...

``` in another way we can say I need to use Spring MVC's controller to expose our rest API, which means requests comes to my controller via url mapping, then...

Quite substantial generics usage. Such a more advanced example has likely not been tested. Have to take a look. Or PR welcomed if you already see the solution.

` class [class ch.emilfrey.dealers.dealer.contractpartners.ContractPartners] has no primary key specified. It should define either an @Id, @EmbeddedId or an @IdClass. If you have defined PK using any of these annotations then...

how does the error look like on the server-side? because I recognize the message, but there is not any stacktrace for it. I pushed a commit that fixes the `{}`...

the error is thrown in the following snippet: ``` String idName = idField.getUnderlyingName(); for (ResourceField relationshipField : relationshipFields) { if (relationshipField.hasIdField() && idName.equals(relationshipField.getIdName())) { parentField = relationshipField; break; } }...

I pushed another commit for the exception message. Is that one better? Nesting is a bit of an advanced `@JsonApiRelationId` use case, so it might be unfamiliar at first but...

It is a bit a dangerous area for changes because of the variety of integrations (servlet, etc.). Where have you seen that `reqestUri != baseUrl + path`? Because that would...