[
https://jira.duraspace.org/browse/DS-1456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=28300#comment-28300
]
Mark H. Wood commented on DS-1456:
----------------------------------
I think the container's classloader hierarchy will defeat this. App.s really
are supposed to be unable to interact through the container. We are going to
have to find something outside the container through which to communicate.
First I would like to settle precisely what is meant by "UIs used". We can't
get a sensible answer to this question statically: installation installs all
the UIs (and a lot of other bits and bobs). I think the only useful meaning
here is "UIs deployed and running in the container." We could define a
database table in which each UI registers itself at startup and deregisters at
shutdown. It would be hard to handle crashes, so I think that anyone wanting
this information would need to verify the current presence of a UI by probing
its base URL, which would be recorded in the table. This also allows us to
have any known UI used to provide paths to other UIs, so for example if you
know that there is a DSpace instance's UI at "http://dspace.example.com/xmlui/";
you could query it and find that there is also a PMH responder at
"http://dspace.example.com/pmh/request"; and a SWORD service at
"http://dspace.example.com/sword/";. (I am using "UI" rather broadly here.)
Well, we shouldn't hack PMH or SWORD to add other-UI-discovery, but XMLUI and
JSPUI (and WebMVC-UI, and, and, and...) should all be able to provide this and
the rest should register/deregister themselves.
> "dspace version" command-line script
> ------------------------------------
>
> Key: DS-1456
> URL: https://jira.duraspace.org/browse/DS-1456
> Project: DSpace
> Issue Type: New Feature
> Reporter: Ivan Masár
> Assignee: Mark H. Wood
> Fix For: 4.0
>
>
> We should provide a "[dspace]/bin/dspace version" script, which would gather
> the basic information about DSpace and its environment that is necessary to
> ask questions on dspace-tech.
> This information includes most prominently:
> * DSpace version
> * OS version
> * UI(s) used
> * is Discovery enabled?
> somewhat less often important:
> * JDK version
> * ant version
> * maven version
> * path to DSpace
> Optional flags could produce even more information, pulled from
> configuration, e.g. database configuration, hostname/URL configuration,
> authentication configuration (with passwords omited), etc.
> Most of this information is already available in the XMLUI admin Control
> panel, so some of those methods could be reused.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. A cloud service to automate IT design, transition and operations
2. Dashboards that offer high-level views of enterprise services
3. A single system of record for all IT processes
http://p.sf.net/sfu/servicenow-d2d-j
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
