[
https://issues.apache.org/jira/browse/OPENJPA-2632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15182758#comment-15182758
]
Romain Manni-Bucau commented on OPENJPA-2632:
---------------------------------------------
[~rsandtner] you are right no restriction but it is an open door to leak - in
particular with the enhancement the spec implies in some cases. What about
adding your patch if a flag is set in the persistence unit properties? If not
set or false then keep current behavior, if set to true use your patch. wdyt?
> select new not working if result class is not in same classloader
> -----------------------------------------------------------------
>
> Key: OPENJPA-2632
> URL: https://issues.apache.org/jira/browse/OPENJPA-2632
> Project: OpenJPA
> Issue Type: Bug
> Components: jdbc
> Affects Versions: 2.4.1
> Reporter: Reinhard Sandtner
> Attachments: OPENJPA-2632.patch
>
>
> in my case i'm using an ear with multiple war files.
> the entities are located in ear/lib and my select new result class and the
> service which loads it are located in a war (doesn't matter if in WEB-INF/lib
> or WEB-INF/classes)
> openJPA uses the CL stored in QueryImpl but this one can not load my class.
> imo if the class can not be loaded with the stored class loader, we can try
> to use the TCCL to load the class.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
