Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unexpected / misleading log on startup #335

Closed
itineric opened this issue Sep 16, 2022 · 2 comments
Closed

Unexpected / misleading log on startup #335

itineric opened this issue Sep 16, 2022 · 2 comments

Comments

@itineric
Copy link

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 ?

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
@Captain-P-Goldfish
Copy link
Owner

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...

@Captain-P-Goldfish
Copy link
Owner

Captain-P-Goldfish commented Sep 17, 2022

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants