User Story #127 (closed)
Opened 13 years ago
Closed 10 years ago
Documentation:: How and where is ROMIO configured?!
| Reported by: | sfrank | Owned by: | cxallan |
|---|---|---|---|
| Priority: | minor | Milestone: | OMERO-Beta4.1 |
| Component: | Configuration | Keywords: | documentation, ROMIO |
| Cc: | Story Points: | n.a. | |
| Sprint: | n.a. | Importance: | n.a. |
| Total Remaining Time: | n.a. | Estimated Remaining Time: | n.a. |
Description
Out-of-the-Box, the Tests for ROMIO fail (at least on windows) with a
java.lang.IllegalArgumentException: Invalid directory specified for file system service.
It is not immediately clear, how ROMIO has to be configured. Are there directories to be created/present when the tests are run?
There should at least be a hint in PixelsService? or AbstractPixelsService?, where parameters for ROMIO can be found. Are there other things that have to/can be configured?
Change History (3)
comment:1 Changed 13 years ago by jmoore
- Milestone set to Unscheduled
comment:2 Changed 10 years ago by cxallan
- Milestone changed from Unscheduled to OMERO-Beta4.1
- Status changed from new to assigned
- Version 3.0-M1 deleted
comment:3 Changed 10 years ago by cxallan
- Resolution set to invalid
- Status changed from assigned to closed
Resolving this as invalid for now. Some of these problems we have put simple solutions in place for, others are just simply a real pain to deal with. We can re-open when we have some specific things here we want to fix.
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
By default, the directory used by ROMIO is specified in AbstractFileSystemService. This may be causing the problems mentioned (stack traces?)
However, the tests for ROMIO (currently still omeio-nio) are split. Part are in the omeio-nio component. However, because of dependencies on values in the DB, other tests are in server to prevent a dependency from omeio-nio on Hibernate. The values here are specified in [trunk/components/server/resources/ome/services/services.xml@688 services.xml], and indeed, there are once again our hard-coded path separators.
Any ideas on ways to specify this in Spring?