Details
-
- Environment:
- -
Issue Links
| Depends | |||
|---|---|---|---|
|
|
|
||
Activity
| Field | Original Value | New Value |
|---|---|---|
| Priority | Blocker [ 1 ] | |
| Description |
Now the registry is contains to kind of information:
- information needed to route messages, - information about service contract. So the registry should be exploded in two parts to be optimized against each use cases: - retrieve service contracts. In this use case performances are not critical, the user should be able to get its WSDL under 1 second, - build the endpoints list against message content. Performance and content of this use case are critical, |
Currently the registry contains two kind of information:
- information needed to route messages, - information about service contract. So the registry should be exploded in two parts to be optimized against each use cases: - retrieve service contracts. In this use case performances are not critical, the user should be able to get its WSDL under 1 second, - build the endpoints list against message content. Performance and content of this use case are critical, |
| Link | This issue blocks SPVEOLIAE-78 [ SPVEOLIAE-78 ] |
| Link |
This issue blocks |
| Status | New [ 10000 ] | Resolved [ 10004 ] |
| Fix Version/s | 5.0.0 [ 10413 ] | |
| Resolution | Fixed [ 1 ] |