[MDSAL-442] Teach binding-dom-codec to keep its proxies in a separate ClassLoader Created: 14/Apr/19  Updated: 29/Apr/19  Resolved: 29/Apr/19

Status: Resolved
Project: mdsal
Component/s: Binding runtime
Affects Version/s: None
Fix Version/s: 4.0.1

Type: Improvement Priority: Medium
Reporter: Robert Varga Assignee: Robert Varga
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Blocks
blocks MDSAL-401 Teach AbstractStreamWriterGenerator t... Resolved
blocks MDSAL-443 Inline CodecDataObject's NodeContextS... Confirmed
is blocked by MDSAL-285 Translate anyxml OpaqueObject to/from... Resolved

 Description   

As a first step towards MDSAL-401 we can start moving DataObject (possibly) and OpaqueObject (definitely) proxies into a separate ClassLoader. Since proxies do not need to load data by themselves, they do not need to reside in the same classloader as the defining type.

The classloader needs to be defined so that it has access to both the target binding class loader as well as to the classloader of binding-dom-codec. A proof that this is really the case will be successful DataObject proxy instantiation.

A real goal here is to turn ForeignOpaqueObject into an abstract class, which is then concretized in the new classloader with the implemented interface – thus forming a baseline for proxy-less invocation.

 



 Comments   
Comment by Robert Varga [ 14/Apr/19 ]

The prototype needs ForeignOpaqueObject for its validation purposes.

Generated at Wed Feb 07 20:09:49 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.