cayenne-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrus Adamchik (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAY-1887) Move class loading under Di, differentiate between Cayenne and application classes
Date Sun, 24 Nov 2013 15:23:35 GMT

    [ https://issues.apache.org/jira/browse/CAY-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13830957#comment-13830957
] 

Andrus Adamchik commented on CAY-1887:
--------------------------------------

only fixed it halfway. OSGi task was implemented with a bit of a hack setting thread classloader.
Still need unwind ObjEntity.getJavaClass and Util.getJavaClass invocations. Specifically inside
EntityResolver. OsgiDataDomainProvider demonstrates what we had to hack.

> Move class loading under Di, differentiate between Cayenne and application classes
> ----------------------------------------------------------------------------------
>
>                 Key: CAY-1887
>                 URL: https://issues.apache.org/jira/browse/CAY-1887
>             Project: Cayenne
>          Issue Type: Task
>            Reporter: Andrus Adamchik
>            Assignee: Andrus Adamchik
>             Fix For: 3.2M2
>
>
> Per CAY-1882 we need to be able to handle class loading under OSGi, with Cayenne sitting
in one bundle, and app code and mapping in another. I think we need to do the following:
> 1. Deprecate the use of static Util.getJavaClass method (which uses static DefaultAdhocObjectFactory),
and change all its invocations to call DI AdhocObjectFactory.
> 2. AdhocObjectFactory must be able to load classes either from Cayenne bundle ClassLoader
(I guess classes coming from org.apache.cayenne?) and application class loader (entity classes,
XML mapping, various extensions).



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message