Petals CDK

JBI API modified... and Petals no more JBI compliant

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Blocker Blocker
  • Resolution: Won't Fix
  • Affects Version/s: 5.2.0
  • Fix Version/s: None
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    javax.jbi.messaging.MessageExchange now has a method called "getProcessInstanceId()".

    This makes Petals JBI-uncompatible, and causes backward-compatibility issues (any JBI component developed for a given version of JBI spec should work on any JBI container implementing the same version of JBI. And in that case, JBI components developed for Petals may not run... on Petals itself (sic)).

    Show
    javax.jbi.messaging.MessageExchange now has a method called "getProcessInstanceId()". This makes Petals JBI-uncompatible, and causes backward-compatibility issues (any JBI component developed for a given version of JBI spec should work on any JBI container implementing the same version of JBI. And in that case, JBI components developed for Petals may not run... on Petals itself (sic)).
  • Environment:
    Any

Activity

Ascending order - Click to sort in descending order
Christophe DENEUX made changes - Fri, 24 Jun 2011 - 16:38:20 +0200
Field Original Value New Value
Project Petals-ESB-Container [ 10029 ] Petals-CDK [ 10032 ]
Key PETALSESBCONT-156 PETALSCDK-59
Affects Version/s 3.1.1 [ 10107 ]
Christophe DENEUX made changes - Fri, 24 Jun 2011 - 16:40:44 +0200
Affects Version/s 5.2.0 [ 10251 ]
Priority Blocker [ 1 ]
Hide
Permalink
Christophe DENEUX added a comment - Fri, 24 Jun 2011 - 16:41:17 +0200

The next version 5.2 of the CDK will not be 100%-compliant with JBI, and all components based on this version can run only on Petals ESB v4.0.0+

Show
Christophe DENEUX added a comment - Fri, 24 Jun 2011 - 16:41:17 +0200 The next version 5.2 of the CDK will not be 100%-compliant with JBI, and all components based on this version can run only on Petals ESB v4.0.0+
Christophe DENEUX made changes - Fri, 24 Jun 2011 - 16:41:17 +0200
Resolution Won't Fix [ 2 ]
Status New [ 10000 ] Resolved [ 10004 ]
Hide
Permalink
mjambert added a comment - Fri, 24 Jun 2011 - 16:44:48 +0200

This what we have been asked for :

  • an old version of a component should keep working in new version of kernel (we ensure that with compatibility tests)
  • a new version of a component might work on an old version of kernel, but is not required to. Otherly said we are allowed to extend JBI and use these extensions in new versions of JBI components.

If you want to use new versions of components, you should better align your kernel on the corresponding version.

Show
mjambert added a comment - Fri, 24 Jun 2011 - 16:44:48 +0200 This what we have been asked for :
  • an old version of a component should keep working in new version of kernel (we ensure that with compatibility tests)
  • a new version of a component might work on an old version of kernel, but is not required to. Otherly said we are allowed to extend JBI and use these extensions in new versions of JBI components.
If you want to use new versions of components, you should better align your kernel on the corresponding version.
Christophe DENEUX made changes - Mon, 10 Oct 2011 - 10:41:29 +0200
Affects Version/s 5.2.0_4.0 [ 10267 ]
Affects Version/s 5.2.0 [ 10251 ]
Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Resolved Resolved
23m 19s
1
Christophe DENEUX
Fri, 24 Jun 2011 - 16:41:17 +0200



People

Dates

  • Created:
    Fri, 24 Jun 2011 - 16:17:58 +0200
    Updated:
    Mon, 10 Oct 2011 - 10:41:29 +0200
    Resolved:
    Fri, 24 Jun 2011 - 16:41:17 +0200
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.