Open brothercorvo opened 2 years ago
the code in https://github.com/GeertBellekens/Enterprise-Architect-Toolpack/blob/master/EAJSON/EAJSONSchema.cs indicate that this has to be a "valid RFC 2396.", and the URL above seems valid to me.
it looks like has nothing to do with the URL. In fact if I reuse the same ID with a custom created model the schema is generated correctly. custom model
ID maybe the tagged value is not correctly applied? I also tried to sync the stereotype with no change
final comment: this is a bug probably related to the application of the JSON profile to existing classes. In fact I can manually replicate a twin class using the toolbox (same ID)
I'll have a look to see if I can reproduce it. Thanks for the detailed analysis
@brothercorvo I tried to reproduce the issue, but I can't make it fail, even when applying the JSON_Schema on an existing class. Could you attach an xmi export of the package containing the problem model?
Sorry, I returned to this after a while. Today I tried to replicate the test and also the second class failed (?!). I created a new class and succeeded. XML attached
I'm trying to transform an existing UML model into a JSON one. After applying the transformations I have the JSON schema assigned. The tagged value ID is filled with a proper URL:
however I get this error message