TOS is filled by endpoints known of a reference environment within EasySOA. Done first by EasySOA calling back TOS so as not to be hindered by EasySOA APi & model changes.
How : TOS opens an Eclipse RCP popup containing a web browser, allowing to browse to EasySOA, and there select environment / services and use a "Send to Eclipse RCP / TOS" button that calls an API (to be defined, no autn) with the following service info : functional name, type info (SOAP, REST/JAXRS/WADL), configuration i.e. URLs for dev/staging/preprod/prod setups
In a second step, remember selected services to allow for easy refresh (of the local cache of known endpoints), and do an impact analysis by using diffs (rather than being readonly).
2. design time discovery :
TOS remotely tells EasySOA which services are being combined within which job being developed. This creates or updates the corresponding "business" view / app in EasySOA in the corresponding "in development" Environment.
How : triggered by an "export" button similar to OSGI export's. The target Environment is chosen in a web popup as in 1. and then remembered.
1. design time registry :
TOS is filled by endpoints known of a reference environment within EasySOA. Done first by EasySOA calling back TOS so as not to be hindered by EasySOA APi & model changes.
How : TOS opens an Eclipse RCP popup containing a web browser, allowing to browse to EasySOA, and there select environment / services and use a "Send to Eclipse RCP / TOS" button that calls an API (to be defined, no autn) with the following service info : functional name, type info (SOAP, REST/JAXRS/WADL), configuration i.e. URLs for dev/staging/preprod/prod setups
In a second step, remember selected services to allow for easy refresh (of the local cache of known endpoints), and do an impact analysis by using diffs (rather than being readonly).
2. design time discovery :
TOS remotely tells EasySOA which services are being combined within which job being developed. This creates or updates the corresponding "business" view / app in EasySOA in the corresponding "in development" Environment.
How : triggered by an "export" button similar to OSGI export's. The target Environment is chosen in a web popup as in 1. and then remembered.