[#PETALSSEQUARTZ-31] Unable to deploy 2 jobs as service consumers of the same service provider defining its endpoint as autogenerated - Petals Link JIRA

Details

Type: Bug
Status: Resolved
Priority: Major
Resolution: Fixed
Affects Version/s: 1.7.0
Fix Version/s: 1.7.1
Component/s: None
Security Level: Public

Description:

Hide

The Quartz job name is computed from interface name, service name and endpoint name. If no endpoint is provided, the value null is used.

So, potential problem can occurs if we want to create jobs to call a same service provider with an autogenerated endpoint (impossible to set the endpoint name at consumer level): one job name identifying two jobs

<jbi:consumes interface-name="mvt:Mouvement" service-name="mvt:MouvementService">
    <petalsCDK:operation>mvt:desactiver</petalsCDK:operation>
    ...
    <quartz:cron-expression>${mouvement.desactivation.cron}</quartz:cron-expression>
    ...
</jbi:consumes>

<jbi:consumes interface-name="mvt:Mouvement" service-name="mvt:MouvementService">
    <petalsCDK:operation>mvt:suspend</petalsCDK:operation>
    ...
    <quartz:cron-expression>${mouvement.suspend.cron}</quartz:cron-expression>
    ...
</jbi:consumes>

So please add support of autogenerated endpoints

Show

The Quartz job name is computed from interface name, service name and endpoint name. If no endpoint is provided, the value null is used. So, potential problem can occurs if we want to create jobs to call a same service provider with an autogenerated endpoint (impossible to set the endpoint name at consumer level): one job name identifying two jobs

<jbi:consumes interface-name="mvt:Mouvement" service-name="mvt:MouvementService">
    <petalsCDK:operation>mvt:desactiver</petalsCDK:operation>
    ...
    <quartz:cron-expression>${mouvement.desactivation.cron}</quartz:cron-expression>
    ...
</jbi:consumes>

<jbi:consumes interface-name="mvt:Mouvement" service-name="mvt:MouvementService">
    <petalsCDK:operation>mvt:suspend</petalsCDK:operation>
    ...
    <quartz:cron-expression>${mouvement.suspend.cron}</quartz:cron-expression>
    ...
</jbi:consumes>

So please add support of autogenerated endpoints

Environment:

-

Activity

Transition

Status Change Time

Execution Times

Last Executer

Last Execution Date

New

Open

2m 44s

Christophe DENEUX

Fri, 24 Jun 2022 - 12:13:22 +0200

Open

In Progress

Christophe DENEUX

Fri, 24 Jun 2022 - 12:13:24 +0200

In Progress

Resolved

24m 8s

Christophe DENEUX

Fri, 24 Jun 2022 - 12:37:32 +0200

Resolved

Open

21s

Christophe DENEUX

Fri, 24 Jun 2022 - 12:37:53 +0200

Open

In Progress

Christophe DENEUX

Fri, 24 Jun 2022 - 12:37:55 +0200

In Progress

Resolved

7m 7s

Christophe DENEUX

Fri, 24 Jun 2022 - 12:45:02 +0200

People

Assignee:

Christophe DENEUX

Reporter:

Christophe DENEUX
Watchers:

0

Dates

Created:

Fri, 24 Jun 2022 - 12:10:38 +0200

Updated:

Fri, 24 Jun 2022 - 12:45:02 +0200

Resolved:

Fri, 24 Jun 2022 - 12:45:02 +0200

Petals BC Quartz

Unable to deploy 2 jobs as service consumers of the same service provider defining its endpoint as autogenerated

Details

Activity

People

Dates