| Summary: | Connection-aware URIs support : default serialization and reconnection management | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Modeling] EMF | Reporter: | Alex Lagarde <alex.lagarde> | ||||||
| Component: | cdo.core | Assignee: | Eike Stepper <stepper> | ||||||
| Status: | CLOSED FIXED | QA Contact: | Eike Stepper <stepper> | ||||||
| Severity: | enhancement | ||||||||
| Priority: | P3 | CC: | esteban.dugueperoux, stepper | ||||||
| Version: | 4.1 | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | All | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
|
Description
Alex Lagarde
Moving all open enhancement requests to 4.1 Would you consider this a duplicate of bug 326186? Now the connection-aware URI works (see the attached JUnit for a example) and CDOSession opening can be customized by providing a CDOViewProvider to the CDOViewProviderRegistry. Created attachment 211419 [details]
JUnit test showing the use of connection aware URI
Created attachment 213163 [details]
JUnit test showing the use of connection aware URI
Sorry the previous attachment was incorrect, now I have attached the correct one, we can considers this bug has closed. Thanks.
Taking test case... commit 4c0ca829c6eeb45344c9af887d24f84ad36a0153 Closing. |