Petals ESB Container

Message Persistance Service should be asynchronous

Details

  • Type: Improvement Request Improvement Request
  • Status: Resolved Resolved
  • Priority: Blocker Blocker
  • Resolution: Won't Fix
  • Affects Version/s: 4.1.0
  • Fix Version/s: 5.0.1
  • Component/s: Persistence
  • Security Level: Public
  • Description:
    Hide

    The current/default persitence service stores messages in a synchronous way (org.ow2.petals.system.persistence.PersistenceServiceImpl#addMessageExchange).
    This operation can be time consuming and should be asynchronous.

    In order to ease the developer life, I suggest to create a PersistenceManager which implements org.ow2.petals.system.persistence.PersistenceService and delegate storage to a default synchronous service. The asynchronous stuff has to be done in the manager.

    Show
    The current/default persitence service stores messages in a synchronous way (org.ow2.petals.system.persistence.PersistenceServiceImpl#addMessageExchange). This operation can be time consuming and should be asynchronous. In order to ease the developer life, I suggest to create a PersistenceManager which implements org.ow2.petals.system.persistence.PersistenceService and delegate storage to a default synchronous service. The asynchronous stuff has to be done in the manager.
  • Environment:
    *

Activity

People

Dates

  • Created:
    Tue, 17 Jul 2012 - 12:24:54 +0200
    Updated:
    Mon, 29 Feb 2016 - 13:06:02 +0100
    Resolved:
    Mon, 29 Feb 2016 - 11:00:37 +0100
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.