Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
COSMOS Design 209234
Change History
Name: | Date: | Revised Sections: |
---|---|---|
Sheldon Lee-Loy | 12/12/2007 |
|
Workload Estimation
Process | Sizing | Names of people doing the work |
---|---|---|
Design | ||
Code | ||
Test | ||
Documentation | ||
Build and infrastructure | ||
Code review, etc.* | ||
TOTAL |
'* - includes other committer work (e.g. check-in, contribution tracking)
Requirement
Error handling is required between the data visualization components (outputters, ODAs) and data collection components (management domain, brokers and data managers).
Design
Data visualization components interact with the data collection components through end point references (EPRs). Web client classes are created that allow the data visualization outputters and ODAs to send SOAP request to various data collection components. This architecture is illustrated below:
The Web client classes will catch soap faults that will be wrapped as java exceptions. Data visualization components will catch these java exceptions. Depending on the exception the data visualization component will either catch and handle the exception or throw the exception to the URLDelegator class. The URLDelegator will act as the last component that will catch any exception and log the exception to error log files.
Note that the data visualization component can send error messages in the HTTP response to the browser client. The browser client would display the error message to the end user.