Closed brianjahnke closed 3 years ago
Thanks for the report. This is a problem with the serializer. Basically, the RDF provided here is just a graph and as such does not need to have something like an obvious root node. Telling the serializer to parse this graph to a Rule gives it some freedom as to which element to choose as the entry point, as there are several rules in here. We are planning to come up with some fix, making the serializer try to find the "root object" in case it has several options to choose from. The fix should be ready within no more than one week.
Hi, this does not seem to be fixed with version 4.0.10. Is this correct? And if so how far is the progress?
Hi @brianjahnke, it seems like we first did the release and then merged the PR with the fix. I have now re-released the 4.0.10 including the fix. Could you please give it another shot?
Hi, the serialization seems to pick the right type now. But this produces quite a lot of log messages (for us), is this intended?
Hi, good point. I have changed it to print the warning only once. Afterward, this message is printed to debug. This enhancement is included in the latest SNAPSHOT and will be released as 4.0.11 on July 5th. Does this resolve the issue?
Hi, could you move the message completly into debug? I think this is not information that should be logged to our users and i would like to not disable logging for the infomodel packages.
All right - debug only it is. Done.
Hi, when we try too deserialize a permission like following this does not result in a permission but only in the contained Post Duty. Changing from Rule.class to Permission.class does fix the problem, but it is not an option in our use case since we do not know the type of the rule. @maboeckmann