Skip to content

[18.0][IMP] edi_webservice_core_oca: add webservice.endpoint support - #367

Open
simahawk wants to merge 4 commits into
OCA:18.0from
camptocamp:18-use-webservice-endpoint
Open

simahawk wants to merge 4 commits into
OCA:18.0from
camptocamp:18-use-webservice-endpoint

Conversation

@simahawk

@simahawk simahawk commented Oct 6, 2026

Copy link
Copy Markdown
Contributor

Depends on

  • [18.0][IMP] webservice_core: add configurable endpoints web-api#175

  • edi.webservice.send handler: now dispatches through a webservice.endpoint
    (mandatory) instead of a raw method/pargs YAML config — method is no longer
    accepted in YAML.

  • edi.exchange.type: new webservice_endpoint_id, webservice_send_as_bytes
    fields, plus a computed webservice_send_enabled (checks send_model_id inherits
    edi.webservice.send via registry) driving the form view.

  • Migration helper (hooks.py, opt-in, not auto-run): migrate_component_based_exchange_types/
    migrate_exchange_type convert exchange types off the legacy component-based send
    onto the new handler — auto-creates the endpoint, splits url_params between
    path-placeholders and querystring, moves send_as_bytes to the new field.

  • Tests and README updated accordingly.

@simahawk simahawk changed the title [18.0][ADD] edi_webservice_core_oca: add webservice.endpoint support [18.0][IMP] edi_webservice_core_oca: add webservice.endpoint support Oct 6, 2026
@OCA-git-bot

Copy link
Copy Markdown
Contributor

Hi @etobella,
some modules you are maintaining are being modified, check this out!

@OCA-git-bot OCA-git-bot added series:18.0 mod:edi_webservice_core_oca Module edi_webservice_core_oca labels Oct 6, 2026

@SilvioC2C SilvioC2C left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would keep the old behavior for backward compatibility, possibly logging a deprecation warning, and remove it completely in v20.0; not blocking though.

@simahawk

Copy link
Copy Markdown
Contributor Author

I would keep the old behavior for backward compatibility, possibly logging a deprecation warning, and remove it completely in v20.0; not blocking though.

The component module keeps the old behavior. Nobody is using the handler model yet -> I don't want to support legacy mode for it 😉

@simahawk
simahawk force-pushed the 18-use-webservice-endpoint branch from 1cbc6d8 to 9ec7908 Compare October 16, 2026 15:09
If the exchange type has a webservice_endpoint_id set, the send handler
uses it directly; otherwise configuration comes from the exchange type's
advanced settings, under execution_model.send.webservice, as before.

send_as_bytes is now a proper field (webservice_send_as_bytes), visible
only when the webservice handler is selected (webservice_send_enabled).
@simahawk
simahawk force-pushed the 18-use-webservice-endpoint branch from 9ec7908 to 35f4d62 Compare October 16, 2026 15:17
@simahawk
simahawk force-pushed the 18-use-webservice-endpoint branch from 35f4d62 to 237db9a Compare October 16, 2026 15:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

mod:edi_webservice_core_oca Module edi_webservice_core_oca series:18.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants