| Redirect | ||
|---|---|---|
|
| Panel | |
|---|---|
On this page:
Target audience: CAST Administrators |
...
For example for the AngularJS extension:
What does it do?
The Web Service Linker automatically creates cross-technology call links between client (front end) and server (back end) objects. For example, AngularJS front end connected to JEE/Spring MVC back end (click to enlarge):
How does it do it?
| Info |
|---|
| End-users do not need to interact or configure the Web Services Linker extension, all configuration is automatic. |
...
The connection is made via four "root" objects:
| HTTP GET Service |
| HTTP DELETE Service |
| HTTP POST/SOAP Service |
| HTTP PUT Service |
| Info |
|---|
| Note that you can view a list of errors and warnings that may potentially be returned during an analysis in Web Services Linker. |
...
- It replace all "//" with "/{}/" except "//" after ":" (to avoid replacing "http://"), supposing that a parameter was intended between both "/" (REST format).
- It removes everything after "?" in the uri (to suppress uri parameters part which are not part of REST format parameters).
- It adds a "/" at the end of uri when not present
| CAST_ResourceService.uri | After transformation |
|---|---|
https://www.castsoftware.com/offices//phone// | https://www.castsoftware.com/offices/{}/phone/{}/ |
https://www.castsoftware.com/offices//phone/ | https://www.castsoftware.com/offices/{}/phone/ |
https://www.castsoftware.com/offices//phone | https://www.castsoftware.com/offices/{}/phone/ |
https://www.castsoftware.com/offices/{}/phone | https://www.castsoftware.com/offices/{}/phone/ |
https://www.castsoftware.com/offices?office=1 | https://www.castsoftware.com/offices/ |
The result is then compared to CAST_WebService_Operation.identification.name / CAST_WebServiceLinker_Operation.identification.name using the endswith function, ignoring the uri part corresponding to the operation name part whose value is {}.
| CAST_ResourceService.uri | CAST_WebService_Operation.identification.name | Match: Yes/No |
|---|---|---|
| .../path1/path2/path3/ | path4/path3/ | No |
| .../path1/path2/path3/{}/ | path3/{}/ | Yes |
| .../path1/path2/path3/ | path2/path3/ | Yes |
| .../param1/value1/param2/value2/ | .../param1/{}/param2/{}/ | Yes |
Examples of matches
A client side url like:
...
- operation name
- port type
Samples
Client side
BPEL
...
Cross-Technology Transaction
| Front-End/Service Exit Point | Back-end/Service Entry Point |
|---|---|
|
|
|