You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am doing some tests with your framework, I have the simpliest server implementation (it does nothing, just starts with a UserHandler and prints out what method is called). It works as expected.
On the first call to the /Users endpoint, the following log is displayed. I cannot find out why or what I am doing wrong.
Do you have a clue ?
INFO de.captaingoldfish.scim.sdk.server.schemas.ResourceTypeFactory - Resource schema with id 'urn:ietf:params:scim:schemas:core:2.0:ServiceProviderConfig' is already registered. The new instance is not equal to the old schema document. The old document is being replaced by the new one
INFO de.captaingoldfish.scim.sdk.server.schemas.ResourceTypeFactory - Resource schema with id 'urn:ietf:params:scim:schemas:core:2.0:ResourceType' is already registered. The new instance is not equal to the old schema document. The old document is being replaced by the new one
INFO de.captaingoldfish.scim.sdk.server.schemas.ResourceTypeFactory - Resource schema with id 'urn:ietf:params:scim:schemas:core:2.0:Schema' is already registered. The new instance is not equal to the old schema document. The old document is being replaced by the new one
The text was updated successfully, but these errors were encountered:
You are not doing anything wrong. It seems that on the first call the schemas seem to be reregistered. I will investigate. I actually fixed this once before... no idea why this is back...
I have no easy reliable fix for this. This seems to be a bug within jackson when comparing arrayNodes with complex objects within it when using the equals method.
Hi,
I am doing some tests with your framework, I have the simpliest server implementation (it does nothing, just starts with a UserHandler and prints out what method is called). It works as expected.
On the first call to the /Users endpoint, the following log is displayed. I cannot find out why or what I am doing wrong.
Do you have a clue ?
The text was updated successfully, but these errors were encountered: