Migrating from 0.4 to easysoa v1.0

mapping old HTTP Proxy monitoring API to new RegistryApi :

for all (Node) :

• title => also build soaname out of it
• description => description IF USEFUL ONLY

old Service to new SoaNodeInformation of type endpoint

• fileUrl => rdi:url for the WSDL URL, endp:url for the endpoint URL
• contentTypeIn/Out => iserv:operationIn/outContentType for each operation (TODO define them for endpoint & refactor ? or even impl ??) and REST ONLY * restinfo:accepts/contentType
• httpMethod => for now within serviceimpl:operations/operationName for JAXRS impls, LATER better for iserv (& endpoint)
• • parentUrl (used for structuring a REST service, which is not supported anymore since rarely useful, but would now go with iserv:operations)
• • callcount (& participants ?) out OPT to state notif
• • rdi:timestamp/probe
• • OPT probe component(s)

old Api has been removed. It was used for structuring a REST service, which is not supported anymore since rarely useful. To support its features :

• sourceUrl => LATER add an OperationNode to structure iserv:operations
• application => if it's the same as AppliImpl then see there, else LATER as a Component gathering several services

old [AppliImpl][(https://github.com/easysoa/EasySOA/blob/master/easysoa-proxy/easysoa-proxy-core/easysoa-proxy-core-api/src/main/java/org/easysoa/proxy/core/api/monitoring/soa/AppliImpl.java) to new SoaNodeInformation of type component with component:category = "application"

• url => nothing more than an extracted URL that should be common to its services.
• appliName => also build SOA name out of it.
• uiUrl => was merely extracted out of URL. LATER maybe add a FunctionalInterface doctype or meta to the model.
• server => was not used (though could be extracted from URL). LATER see again when updating runtime management features.
• sourcesUrl => was not used. Now somehow platform:deliverableRepositoryUrl and deltype:repositoryUrl.
• standard => was not used. Now platform:serviceLanguage & impl:technology.
• technology => was not used. Now platform:serviceRuntime & endpoint:serviceRuntime.

mapping old easysoa-registry-api-remote API to new RegistryApi :

for all (old EasySOADoctype) :

• see above mapping
• discoveryTypeBrowsing/Monitoring/Import/Design
• archiPath/LocalName => Components of various types encompassing InformationServices, LATER also as computed archiPath starting with actor
• environment => endp:enviromnent

old Service to new InformationService and Endpoint :

• see above mapping
• wsdlNamespace/ServiceName => wsdlinfo:wsdlServiceName, but even more important is wsdlinfo:wsdlPortTypeName
• referenceService(Origin) => split now among an impl/endpoint's expected InformationService, iserv/impl/endpoint versioning + diff and LATER to be updated global comparison between environments
• isValidated/validationState(validatorName, validationLog) => split now among an impl/endpoint's matchinf (or not) InformationService, iserv/impl/endpoint diff between versions and LATER to be updated global comparison/validation between environments
• lightUrl => LATER URL to scaffolder, built from (ExchangeRecordSet)Samples registered on the iserv/endpoint
• fileUrl => rdi:url on iserv/endoint, LATER on all (WsdlInterface/Policy)Resources

old ServiceReference to new (Java)Service/EndpointConsumption :

• refId/Url => consumedClass/Interface(Location), LATER also on endpoint

old Api :

• see above mapping
• protocols => platform:serviceLanguage & impl:technology or platform:serviceProtocol endpoint:serviceProtocol ?

old AppliImpl to new SoaNodeInformation of type component with component:category = "application" :

• see above mapping
• provider => Actor, iserv:providerActor etc.
• designDocumentName/Source => RequirementsDocument and especially TODO
• runtimeServer => platform:appServerRuntime and endpoint:appServerRuntime, LATER see again when updating runtime management features.
• deployableProvider => Now platform:deliverableRepositoryUrl and deltype:repositoryUrl
• deployables(deployableId/Name/Version) => del:dependencies, LATER see again when updating runtime management features.
• lifeCycleStatus

old Workspace to new Subproject (Phase) of SoaNodeInformation

• referencedEnvironment, isValidated/validationLog => LATER 1. aggregated indicators of validation of its SOA elements and 2. to be updated global comparison/validation between environments