| 1 | == XGAP-DAS connection project == |
| 2 | |
| 3 | The DAS servlet itself is served directly from the source, it cannot be edited: |
| 4 | {{{ |
| 5 | <servlet> |
| 6 | <servlet-name>DasServlet</servlet-name> |
| 7 | <servlet-class>uk.ac.ebi.mydas.controller.MydasServlet</servlet-class> |
| 8 | </servlet> |
| 9 | <servlet-mapping> |
| 10 | <servlet-name>DasServlet</servlet-name> |
| 11 | <url-pattern>/das/*</url-pattern> |
| 12 | </servlet-mapping> |
| 13 | }}} |
| 14 | |
| 15 | The servlet reads a file named 'MydasServerConfig.xml' located in the WebContent folder. |
| 16 | |
| 17 | Inside MydasServerConfig.xml, all needed properties are set. For example: |
| 18 | |
| 19 | * URL of the DAS server (ie. XGAP application running on some IP adress) |
| 20 | * XSLT transformation services of the DAS output |
| 21 | * Default stylesheet for data sources |
| 22 | |
| 23 | The important bits are in the datasources section. Here we define what data goes into the DAS service. In the example: |
| 24 | |
| 25 | * We point to a class file: <class>mydas.examples.EnsemblTestDataSource</class> |
| 26 | * A coordinate system is entered, needed to map the data to other DAS sources |
| 27 | * The capabilities are defined. We tell DAS what this datasource can provide. |
| 28 | |
| 29 | What we want is: |
| 30 | |
| 31 | Phase 1. |
| 32 | |
| 33 | * New datasource(s) that provide data from an XGAP database in the form of class file(s). |
| 34 | * Proper configuration of this source in the config xml. |
| 35 | * A working connection to a DAS client |
| 36 | |
| 37 | Phase 2. |
| 38 | |
| 39 | * A plugin to 'edit' the config xml. For example, adjust organism and coordinate system. |
| 40 | * Smart datasource/config files that serve out the data they can provide, depending on what is in the database. |
| 41 | * A client integrated in XGAP that uses our own data as a source |
| 42 | * Expanding the client so it uses other sources as well, build a plugin around this to the user can quickly add/remove sources |
| 43 | |
| 44 | The last two can be done by eg. IFRAMing an existing client and entering our application URL to the list of sources, making use of existing software and source listings. |