Task #314 (closed)
Opened 18 years ago
Closed 16 years ago
Permit generic lookup of services from ServiceFactory
| Reported by: | jamoore | Owned by: | jamoore |
|---|---|---|---|
| Priority: | minor | Milestone: | 3.0-Beta3 |
| Component: | Configuration | Version: | 3.0-M3 |
| Keywords: | spring,jndi,services | Cc: | |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description (last modified by jmoore)
All lookup methods in ServiceFactory delegate to the method getServiceByClass(Class<? extends ServiceInterface>). This could be made public so that new service additions do not require an update to ServiceFactory.
Further, if the Spring lookup fails, an attempt to locate "omero/remote/<class name>" or "omero/local/<class name>" in JNDI could be made. (Also, document these JNDI names and perhaps add an config object like Server & Login)
Change History (4)
comment:1 Changed 18 years ago by jmoore
comment:2 Changed 18 years ago by jmoore
Should be noted that even without the changes mentioned here, it is, strictly speaking, possible to get to any service without changing ServiceFactory or ome/client/spring.xml by directly using JNDI and JAAS. Not pretty but doable. Should perhaps also be documented.
comment:3 Changed 18 years ago by jmoore
- Milestone changed from 3.0-M3 to Future
comment:4 Changed 16 years ago by jmoore
- Description modified (diff)
- Milestone changed from Future to 3.0-Beta3
- Resolution set to fixed
- Status changed from new to closed
Completed with r1900
This would also allow one to add a new service without modifying any existing files, i.e. one could drop in a jar or similar and have it available (barring some class loader issues between EARs and JARs). See r905 for comparison, where two files had to be edited.