[jira] [Resolved] (OWB-931) NormalScopeProxyFactory classloader usage

["Mark Struberg (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OWB-931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Struberg resolved OWB-931.
-------------------------------
       Resolution: Fixed
    Fix Version/s: 1.5.0
         Assignee: Mark Struberg

This should be resolved by the introduction of ApplicationBoundaryService. Please ping back if this doesn't fit your need - txs!

> NormalScopeProxyFactory classloader usage
> -----------------------------------------
>
>                 Key: OWB-931
>                 URL: https://issues.apache.org/jira/browse/OWB-931
>             Project: OpenWebBeans
>          Issue Type: Brainstorming
>          Components: Core
>    Affects Versions: 1.2.0
>            Reporter: Moritz Bechler
>            Assignee: Mark Struberg
>              Labels: ClassLoader, OSGI
>             Fix For: 1.5.0
>
>         Attachments: OWB-931-v1.patch, OWB-931-v2-trunk.patch, OWB-931-v2.patch
>
>
> createNormalScopeProxy currently uses the bean class ClassLoader for two purposes:
> 1. defining the proxy class
> 2. instantiation of the instance provider.
> In our OSGI/WAB environment this usage does not make much sense:
> 1. the proxy class should be defined in the classloader which most closely reflects the CDI context lifecycle, which is the web context TCCL. 
> 2. causes trouble with scope providers (e.g OWB's own RequestScopedBeanInterceptorHandler) when they are defined in another bundle. I don't think there is a proper compatible solution to this (except maybe making extensions fragments) but also trying the TCCL makes this much more painless to use.
> Is there any explanation for this particular choice of classloaders? Are there any reasons not to try TCCL first?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)