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.
Talk:COSMOS Design 215123
Revision as of 13:31, 4 February 2008 by Unnamed Poltroon (Talk) (New page: *The data manager client now has an API for getting the WSDL from the data manager. MEX client is used to get the WSDL. ** Need pluggable ways to get wsdl. i.e. the client should be able...)
- The data manager client now has an API for getting the WSDL from the data manager. MEX client is used to get the WSDL.
- Need pluggable ways to get wsdl. i.e. the client should be able to use different mechanisms to retrive WSDL from the data manager. This is important if the client needs to communicate non-COSMOS MDRs.
- Ways to get WSDL include:
- ?wsdl (Axis2)
- MEX
- We need an API for getting the metadata information in POJO representation. The goal is to avoid the need to manipulation of XML and WSDL as musch as posible.
- The comment about using POJO applies to query and registration APIs as well. i.e. the parameters of the operation and the return value should use POJO where possible.
- Where to MDR metadata be stored?
- MDR: metadata is configured and stored at the MDR. Client can always query an MDR for its metadata.
- Broker: Broker can cache values or properties about MDRs that can help categorize the broker. The values cached at the broker are used as search critera when querying for data manager EPRs. Some "service level" metadata (such as query capabilities) are not useful at the broker.
- Values defined in the CMDBf service metatdata that may be useful at the broker include:
- serviceDescription/mdrId
- serviceDescription/description
- Values defined in the CMDBf service metatdata that may be useful at the broker include:
Related topics for discussion:
- How to keep cache values at the broker up-to-date?
- How to configure service metadata values at MDRs?