[
http://jira.dspace.org/jira/browse/DS-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stuart Lewis updated DS-516:
----------------------------
Fix Version/s: (was: 1.6.1)
1.7
Committed to 1.6x branch. Will leave open until we have reached consensus about
how to apply to 1.7. Main decision needed: do we delete all the bin scripts
that call dsrun?
> DSRUN does not start Service Manager
> ------------------------------------
>
> Key: DS-516
> URL: http://jira.dspace.org/jira/browse/DS-516
> Project: DSpace 1.x
> Issue Type: Bug
> Components: DSpace API
> Affects Versions: 1.6.0
> Reporter: Mark Diggory
> Assignee: Stuart Lewis
> Fix For: 1.7
>
> Attachments: DS-516-v2.patch, DS-516-v3.patch, DS-516-v4Tim.patch,
> dsrun.patch
>
>
> I'll also comment you'll want to use the "dspace" CLI script to launch
> executions rather than "dsrun" as the DSpace services framework need to be
> started properly before updates happen to services.
> Comment to the developers... We rather missed this in our architecture of the
> new execution environment. We may want to consider removing dsrun or
> enabling a Main wrapper around it similar to the "dspace" shell runner so
> that the Spring/Services framework is properly started. An alternative would
> be to make "dspace" more flexible to support passing Classnames directly to
> it in the same manner as "dsrun".
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.dspace.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
