On Fri, Apr 23, 2010 at 1:24 PM, Mark H. Wood <[email protected]> wrote: > On Fri, Apr 23, 2010 at 12:16:35PM -0700, Mark Diggory wrote: >> Yep, exactly the reason to use a common repository.... I do have a copy of >> that floating around my workstation, but I will warn you it is very broken, >> I'll see if I can recovery it for you. > > Thank you! Broken I can fix, but missing would have meant I have to > learn both ends of JMS from scratch at once, using the rather murky JMS > and ActiveMQ documentation.
I worry that this will be misleading, let me tell you where the work left off. We extracted this from the Event System because of how closely tied it was to replacing the event manager and dispatchers. Likewise, how closely it was tied to JMS. the Event System then evolved separately to be available for DSpace 1.5. So your going to have to be doing two things. (1) figuring out what is happening in the code and (2) correcting it to work with the Event System. Where we left off with development was in dropping the use of a customized Dispatcher/EventManager just for Asynchronous eventing. And instead looking to move any ties to JMS into the Consumer so that there was less being replaced in the EventManager/Dispatcher. >> Speaking of Asynchronous Eventing.... I just wrote a Spring/Quartz job >> scheduling service for the dspace-services project, would you be interested >> in that? Next steps were to write some example jobs that could be >> fired asynchronously by EventListeners and run concurrently in the >> background. > > That could be useful. I'm exploring ways to capture data model > changes for offsite backup, without making contributors/admin.s wait > for an export every time they change something. Yes, I was looking get the same returns out of it for updating Search/Browse and possibly applying FilterMedia after the submission process. Ultimately I was looking to do away with needing external crons / schedules outside of DSpace, allowing work to get done in the same user and JVM process that the UI are running in. I was beginning to submit a JIRA ticket on the topic... http://jira.dspace.org/jira/browse/DSRV-5 Next steps were to look into creating a few Quartz Jobs that reflected real DSpace activities and adding them to another maven project that would be dependent on both dspace-services and dspace-api. Then, looking to create an XMLUI Aspect that would be used to review, add, delete, schedule, pause and restart jobs. Mark -- Mark R. Diggory Head of U.S. Operations - @mire http://www.atmire.com - Institutional Repository Solutions http://www.togather.eu - Before getting together, get t...@ther ------------------------------------------------------------------------------ _______________________________________________ Dspace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-devel
