| 6 | |
| 7 | = Related DataOpeners to DataSources = |
| 8 | At the end, the dataopeners are tightly knit to datasources, not to URI-scheme. |
| 9 | The method DataOpenerRegistry.get(String urischeme) is not good. |
| 10 | |
| 11 | As we have the uri scheme "gnowsis://" quite often for Outlook, Thunderbird, some other stuff. |
| 12 | |
| 13 | Still, opening by URI scheme is a good fallback when I have a resource at hand from which i know only URI (and not the originating datasource) so I would keep it as fallback. |
| 14 | |
| 15 | Idea: |
| 16 | * Add a new method to DataSource - getDataOpener which returns an instance of DataOpener (or uses the DataOpenerRegistry internally, when not defining own DataOpeners). |