[
https://issues.apache.org/jira/browse/OPENJPA-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18142008#comment-18142008
]
ASF subversion and git services commented on OPENJPA-3071:
----------------------------------------------------------
Commit e3c9055534c08b94fc4d40f6c132aa4e7e0e4694 in openjpa's branch
refs/heads/master from Richard Zowalla
[ https://gitbox.apache.org/repos/asf?p=openjpa.git;h=e3c905553 ]
[OPENJPA-3071] Resolve type names of remote commit events through the metadata
repository
The data and query caches turned the type names of a remote commit event
into classes with Class.forName, which loaded and initialized any named
class. Look the names up among the persistent types known to the metadata
repository and the registered persistent types instead, and ignore other
names.
ClassResolvingObjectInputStream now also checks the interface names of
dynamic proxies against the class blacklist before resolving the proxy
class through its candidate loaders.
> Resolve type names of remote commit events through the metadata repository
> --------------------------------------------------------------------------
>
> Key: OPENJPA-3071
> URL: https://issues.apache.org/jira/browse/OPENJPA-3071
> Project: OpenJPA
> Issue Type: Improvement
> Reporter: Richard Zowalla
> Assignee: Richard Zowalla
> Priority: Major
> Fix For: 4.2.0
>
>
> When a remote commit event arrives, the data and query caches turn the type
> names it contains into classes with Class.forName, which also loads and
> initializes classes that are not persistent types. Look the names up in the
> metadata repository instead and ignore unknown names. Also check the
> interface names of dynamic proxies when OpenJPA reads serialized objects,
> like it does for class names.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
