Petals ESB Container

Migration of hack about moving a DOMSource as read-only

Details

  • Type: Task Task
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 5.2.0
  • Fix Version/s: 5.3.0, 5.4.0
  • Component/s: Micro-kernel
  • Security Level: Public
  • Description:
    Hide

    When a DOMSource is put as content for a message, it is set as readonly to prevent concurrent modification between service provider, service consumer and others.

    As the JDK internal Xerces is used as DOM parser, the JDK internal classes are used for the hack to set DOM nodes as readonly.

    With Java 11, we are not able to access the JDK internal classes. We may find a workaround.

    Show
    When a DOMSource is put as content for a message, it is set as readonly to prevent concurrent modification between service provider, service consumer and others. As the JDK internal Xerces is used as DOM parser, the JDK internal classes are used for the hack to set DOM nodes as readonly. With Java 11, we are not able to access the JDK internal classes. We may find a workaround.
  • Environment:
    -

Issue Links

Depends

People

Dates

  • Created:
    Tue, 16 Feb 2021 - 10:39:29 +0100
    Updated:
    Thu, 13 Apr 2023 - 16:58:06 +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.