Petals ESB Container

Migration of hack about moving a DOMSource as read-only

View this issue in another formatViewView
- XML
- Word
- Printable

Details

Type: Task
Status: Open
Priority: 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

This issue depends on:
PETALSDISTRIB-467 Remove access to internal classes

This issue blocks:
~~PETALSDISTRIB-416~~ Move to Java 11

Activity

Transition

Status Change Time

Execution Times

Last Executer

Last Execution Date

New

Open

14s

1

Christophe DENEUX

Tue, 16 Feb 2021 - 10:39:43 +0100

Open

In Progress

6s

1

Christophe DENEUX

Tue, 16 Feb 2021 - 10:39:49 +0100

In Progress

Resolved

2m 46s

1

Christophe DENEUX

Tue, 16 Feb 2021 - 10:42:35 +0100

Resolved

Open

14s

1

Christophe DENEUX

Tue, 16 Feb 2021 - 10:42:49 +0100

People

Assignee:

Christophe DENEUX

Reporter:

Christophe DENEUX
Watchers:

0

Dates

Created:

Tue, 16 Feb 2021 - 10:39:29 +0100

Updated:

Thu, 13 Apr 2023 - 16:58:06 +0200