Opened 11 years ago
Closed 9 years ago
#347 closed enhancement (fixed)
Version identification in user interface
| Reported by: | keeloo | Owned by: | Sander Maijers |
|---|---|---|---|
| Priority: | trivial | Milestone: | VLO-3.2 |
| Component: | VLO web app | Version: | |
| Keywords: | version user interface | Cc: | Dieter Van Uytvanck, teckart@informatik.uni-leipzig.de |
Description (last modified by )
Add an indication of the version running to the web application's user interface. Next to the version number, 'beta' should appear if the application is running in beta. Since this cannot be inferred from the version number, a parameter in the configuration file indicating the beta status should be sufficient.
Preferably, the 'beta' indication should appear in the
back to results | no original context available | found an error?
line in the results page.
Change History (12)
comment:1 Changed 11 years ago by
| Cc: | teckart added |
|---|
comment:2 Changed 11 years ago by
| Description: | modified (diff) |
|---|
comment:3 Changed 11 years ago by
comment:4 Changed 10 years ago by
| Owner: | changed from sanmai to Sander Maijers |
|---|---|
| Status: | new → assigned |
comment:5 Changed 10 years ago by
| Cc: | Dieter Van Uytvanck teckart@informatik.uni-leipzig.de added; teckart removed |
|---|---|
| Milestone: | → VLO-3.1 |
VLO version number is shown in the footer. For beta releases, 'beta' is included in the version identifier. Assuming this is sufficient, or should the 'beta' indication be more prominent? In that case I would suggest using a context parameter or JVM System Property to toggle a label in a clearly visible but non-intrusive place in the layout.
comment:6 Changed 10 years ago by
That is sufficient in my opinion.
Taking it further, for debugging purposes you may still want to provide some HTTP based means to provide (application) context information: https://tomcat.apache.org/tomcat-7.0-doc/api/org/apache/catalina/core/ApplicationContext.html . When a user has a problem with a VLO instance and the Tomcat instance is equivocal to him/her, the LAT admins may lose time in solving service problems.
Esp. if it's on a separate URL path the UI and security wouldn't suffer from this.
comment:7 Changed 10 years ago by
That's a good suggestion. Are you aware of any existing solutions (e.g. a stand-alone servlet or JSP page) that present the context in a secure and somewhat user friendly manner?
comment:10 Changed 10 years ago by
| Priority: | minor → trivial |
|---|
comment:11 Changed 9 years ago by
| Milestone: | VLO-3.1 → VLO-3.2 |
|---|
Splitting 3.1 milestone. Most open tickets go to 3.2 so that we can have a release on the short term.
comment:12 Changed 9 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Suggestion: show Tomcat instance info instead of separately specifying whether or not a VLO instance is beta in a configuration file. I don't know whether this is practically possible but if it is, I believe it would be preferable since it allows more flexibility (potentially not just distinction beta/production) and infers values instead of specifying them (less redundancy).