Helio, thanks again for continuing to evaluate Artificer. This week, I'm planning to write a few blog posts, as well as re-write the overview in the Artificer docs, that will hopefully answer most of your questions. After that, ping me if there are still clarifications that would be helpful? Thanks!
Yes, blog posts would be great !
"...What if I, a member of a development team within the company, want to update, replace, or create a new version of that schema? What services and what teams will be impacted? Even more specifically, what will be impacted if I change a single type in the schema? "
very clear +1
"Looks like 'Service Endpoint ABC' is defined by that WSDL service. Who is responsible for the endpoint?
*** Result: 'provides' <-- Team XYZ (Organization)
Alright, so 'Team XYZ' is responsible for 'Service Endpoint ABC'.
Better contact them and let them know why things are about to break...
More specifically, I only want to change one single type declaration: 'extOutputType'.
Within *all* WSDLs in the repo, what exactly is using that type? Again, look at the relationships targeting it.
*** Result: 'type' <-- parameters (Part)
Ok, one Part. Keep going. Which Message?
*** Result: 'part' <-- findResponse (Message)
Found the Message. Now where is it used?
*** Result: 'message' <-- findResponse (OperationOutput)
An OperationOutput. Which Operation?
*** Result: 'output' <-- find (Operation)
Now I know exactly which pieces of the WSDL will be affected!