| Key: |
COR-2015
|
| Type: |
Bug
|
| Status: |
Open
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Patrick Roemer
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
Environment:
|
Java
|
|
Issue Links:
|
Related
|
|
|
|
This issue is related to:
|
|
DOC-535
Document Load time instrumentation configuration gotcha
|
|
|
|
|
|
|
| Order: |
4
|
| Labels: |
|
| Participants: |
Patrick Roemer
|
| Number of Attachments: |
0
|
| Number of Comments: |
0
|
|
Db4oEnhancedLauncher/Db4oInstrumentationLauncher only set up the thread context CL to point to the instrumenting CL. If db4o is not explicitly configured to reflect against the context CL, the user space objects will be loaded by the instrumenting CL, while the db4o reflector layer will only see the app CL, resulting in a ClassCastException upon store/retrieve.
Workaround:
config.common().reflectWith(Thread.currentThread().getContextClassLoader());
Even if we just accept this behavior, it needs to be documented and we need a test case.
|
|
Description
|
Db4oEnhancedLauncher/Db4oInstrumentationLauncher only set up the thread context CL to point to the instrumenting CL. If db4o is not explicitly configured to reflect against the context CL, the user space objects will be loaded by the instrumenting CL, while the db4o reflector layer will only see the app CL, resulting in a ClassCastException upon store/retrieve.
Workaround:
config.common().reflectWith(Thread.currentThread().getContextClassLoader());
Even if we just accept this behavior, it needs to be documented and we need a test case. |
Show » |
| There are no comments yet on this issue.
|
|
Load time instrumentation relies on client code to configure db4o to use context classloader 