Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "COSMOS Design 209227"
m (→Topics to cover in the design doc) |
(→Topics to cover in the design doc) |
||
Line 65: | Line 65: | ||
* What is our taxonomy of faults? | * What is our taxonomy of faults? | ||
+ | * How do you extend the framework? | ||
+ | DataManagerExeption class | ||
Revision as of 14:16, 12 November 2007
Topics to cover in the design doc
- logfile registry & viewer
- error/warning event pub/sub
- cbe v. wef
- msg formats & IDs (valentina to help here)
- resource modeling
- repository
- sml tool
What's out of scope:
- Logging handled by Jimmy's enhancement (but this is related).
- eclipse tooling
- Out of scope for this enhancement
What's in scope:
- How do you propagate the problems:
- Internally w/in a component
- Between components
Error handling discussion
2 runtime environments: - eclipse tooling
- Out of scope for this enhancement
- Server Environment is the focus
- runtime outside eclipse (our focus for these 2 bugs) - OSGi & J2EE (Tomcat)
Components:
- Domain
- Broker
- MDR/Data manager
-> Each component will keep its own log file -> can use tooling (TPTP) to merge them when doing analysis
Log format - Java logging - muse logging (?) - any transaction ID to inject into log record for correlation
Error code
Translation
- Message catalogs
Exception Handling
- between client and server (SOAP Faults)
- between UI and DC client
-
- Do not want to expose the soap faults to: a) the user b) the adopter
- What are the standard faults declared by the specification
- What is the nesting strategy of exceptions
- What is our taxonomy of faults?
- How do you extend the framework?
DataManagerExeption class
- What about symptoms?