Petals SE POJO

Unable to manage expired asynch message in su-pojo

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: 2.2.6
  • Fix Version/s: 2.2.7, 2.3.0
  • Component/s: None
  • Security Level: Public
  • Description:

    The JBIListener.onExpiredAsyncJBIMessage method , just return false.

    So we can't manage expired asynch message in a su-pojo.

  • Environment:
    Petals 3.1.3
    windows xp
  1. petals-se-pojo-2.2.7-SNAPSHOT.zip
    (4.99 MB)
    Christophe DENEUX
    Sat, 17 Mar 2012 - 11:55:13 +0100

Activity

Hide
Christophe DENEUX added a comment - Sat, 17 Mar 2012 - 11:28:30 +0100

Attached a SE POJO managing expired async method. Add the following method in your POJO class: {{onExpiredAsyncExchange(Exchange, AsyncContext).

This implementation has not been tested

Show
Christophe DENEUX added a comment - Sat, 17 Mar 2012 - 11:28:30 +0100 Attached a SE POJO managing expired async method. Add the following method in your POJO class: {{onExpiredAsyncExchange(Exchange, AsyncContext). This implementation has not been tested
Hide
Christophe DENEUX added a comment - Thu, 22 Mar 2012 - 13:10:10 +0100

Fixed in branch petals-enterprise-3.1.x

Show
Christophe DENEUX added a comment - Thu, 22 Mar 2012 - 13:10:10 +0100 Fixed in branch petals-enterprise-3.1.x
Hide
Christophe DENEUX added a comment - Thu, 22 Mar 2012 - 13:10:24 +0100

To merge in trunk

Show
Christophe DENEUX added a comment - Thu, 22 Mar 2012 - 13:10:24 +0100 To merge in trunk
Hide
Christophe DENEUX added a comment - Mon, 26 Mar 2012 - 15:02:33 +0200

Merged in trunk

Show
Christophe DENEUX added a comment - Mon, 26 Mar 2012 - 15:02:33 +0200 Merged in trunk

People

Dates

  • Created:
    Thu, 15 Mar 2012 - 17:15:00 +0100
    Updated:
    Mon, 26 Mar 2012 - 15:02:33 +0200
    Resolved:
    Mon, 26 Mar 2012 - 15:02:33 +0200