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.
Difference between revisions of "Corona CC Model Changes"
| Line 1: | Line 1: | ||
First of all I think we need to define [[Corona CC use cases|use cases]] and see if we can support it with current model. | First of all I think we need to define [[Corona CC use cases|use cases]] and see if we can support it with current model. | ||
| + | |||
| + | == ContextContainer == | ||
| + | The ContextContainer (and ProjectContainer) classes are generated from an EMF model. Additional methods need to be added to these classes as well as updating the functionality provided by some of the generated methods. | ||
| + | * Modify our usage of EMF to generate the model from annotations from the ContextContainer interface instead of schema | ||
| + | * Create a JET template to use by EMF/SDO code generation to merge new functionality as well as update existing methods | ||
| + | * ContextContainer.postEvent() | ||
| + | ** Estabalish the only way to post a container event is by using the container's postEvent() method. | ||
| + | ** Refactor non-container event posting mechanisms as ''internal''. | ||
| + | ** Annotate the postEvent() for WS-Notification | ||
| + | * ContextContainer.addEventHandler() | ||
| + | ** Estabalish the only way to add a container event listener is by using the container's addEventHandler() method. | ||
| + | ** Refactor non-container event handler mechanisms as ''internal''. | ||
| + | * ContextContainer add/update/delete methods | ||
| + | ** embed within each add/update/delete methods an invocation of postEvent() to notify the collaboration environment that the container has been modified. | ||
| + | * Common ProjectContainer functionality | ||
| + | ** Refactory ProjectContainer to move any non-Project specific functionality to the ContextContainer | ||
== Content-format attribute in repository - [https://bugs.eclipse.org/bugs/show_bug.cgi?id=168680 bug 168680] == | == Content-format attribute in repository - [https://bugs.eclipse.org/bugs/show_bug.cgi?id=168680 bug 168680] == | ||
All details in [https://bugs.eclipse.org/bugs/show_bug.cgi?id=168680 the bug]. | All details in [https://bugs.eclipse.org/bugs/show_bug.cgi?id=168680 the bug]. | ||
Revision as of 20:56, 28 February 2007
First of all I think we need to define use cases and see if we can support it with current model.
ContextContainer
The ContextContainer (and ProjectContainer) classes are generated from an EMF model. Additional methods need to be added to these classes as well as updating the functionality provided by some of the generated methods.
- Modify our usage of EMF to generate the model from annotations from the ContextContainer interface instead of schema
- Create a JET template to use by EMF/SDO code generation to merge new functionality as well as update existing methods
- ContextContainer.postEvent()
- Estabalish the only way to post a container event is by using the container's postEvent() method.
- Refactor non-container event posting mechanisms as internal.
- Annotate the postEvent() for WS-Notification
- ContextContainer.addEventHandler()
- Estabalish the only way to add a container event listener is by using the container's addEventHandler() method.
- Refactor non-container event handler mechanisms as internal.
- ContextContainer add/update/delete methods
- embed within each add/update/delete methods an invocation of postEvent() to notify the collaboration environment that the container has been modified.
- Common ProjectContainer functionality
- Refactory ProjectContainer to move any non-Project specific functionality to the ContextContainer
Content-format attribute in repository - bug 168680
All details in the bug.
Resource id for content adapter
We intend to make a layered architecture there there is repository adapter and content adapter. The content adapter would parse resource returned by repository adapter. So, the content adapter needs to know the argument to call fetchResource() with.
Eg. We have a team member XML file in CVS. Repository adapter is used to connect CVS. Content adapter is used to parse the file. But how the content adapter know which file to choose?
Should it be some predefined repository connection?