Bug #313 (closed)
Opened 18 years ago
Closed 18 years ago
OmeroContext is throwing exceptions on missing properties too early.
Reported by: | jamoore | Owned by: | jamoore |
---|---|---|---|
Priority: | critical | Cc: | jburel, bwzloranger, cxallan |
Sprint: | n.a. | ||
Total Remaining Time: | n.a. |
Description (last modified by jmoore)
The exceptions that client users/developers have been seeing during login are due to the extra call to ApplicationContext.refresh specified by the client/resources/beanRefContext.xml file. If we change this to "false" and perform checks in OmeroContext, then this should go away.
Change History (6)
comment:1 Changed 18 years ago by jmoore
- Description modified (diff)
comment:2 Changed 18 years ago by jmoore
comment:3 Changed 18 years ago by jmoore
comment:4 Changed 18 years ago by jmoore
r898 removes a piece of this changeset that will be re-added later.
comment:5 Changed 18 years ago by jmoore
r912 fixes the omero.rootpass issue by throwing the rootLogin bean out of ome/client/spring.xml and into ome/testing/data.xml
comment:6 Changed 18 years ago by jmoore
- Cc callan added
- Resolution set to fixed
- Status changed from new to closed
Clients now seem to be able to login without issue. (I.e. without needing to call System.setProperty(...,...). Closing.
Also, to make this work, we're including all the non-sensitive properties files from /etc in the client jar. This should make things a good deal simpler. At some point, these may need to be removed and put in a omero-etc.jar or similar, but for the moment these things just aren't that variable. All currently important variables can be overwritten with Server & Login.