Petals BC Quartz

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

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major 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

Ascending order - Click to sort in descending order
Hide
Permalink
Christophe DENEUX added a comment - Fri, 24 Jun 2022 - 12:37:32 +0200

Fixed in branch petals-bc-quartz-1.6.x

Show
Christophe DENEUX added a comment - Fri, 24 Jun 2022 - 12:37:32 +0200 Fixed in branch petals-bc-quartz-1.6.x
Hide
Permalink
Christophe DENEUX added a comment - Fri, 24 Jun 2022 - 12:37:53 +0200

Reopened to merge in trunk

Show
Christophe DENEUX added a comment - Fri, 24 Jun 2022 - 12:37:53 +0200 Reopened to merge in trunk
Hide
Permalink
Christophe DENEUX added a comment - Fri, 24 Jun 2022 - 12:45:02 +0200

Merged in trunk

Show
Christophe DENEUX added a comment - Fri, 24 Jun 2022 - 12:45:02 +0200 Merged in trunk

People

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
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.