[jira] Commented: (OWB-496) Don't replace the ProxyFactory classloaderProvider without the intention to do so

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

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

Mark Struberg commented on OWB-496:
-----------------------------------

question: why is the fallback not _true_ by default?
or: why do we need this fallback at all?

The bug only have been that the ProxyFactory.classloaderProvider got changed and not subsequently resetted - resulting in an invalid behaviour.

But by _resetting_ it in the final block (btw, shouldn't we synchronize this?) this negative effect got fixed already, isn't?

> Don't replace the ProxyFactory classloaderProvider without the intention to do so
> ---------------------------------------------------------------------------------
>
>                 Key: OWB-496
>                 URL: https://issues.apache.org/jira/browse/OWB-496
>             Project: OpenWebBeans
>          Issue Type: Bug
>          Components: Context and Scopes
>    Affects Versions: 1.1.0
>            Reporter: David Jencks
>            Assignee: Gurkan Erdogdu
>             Fix For: 1.1.0
>
>
> Currently JavassistProxyFactory.getProxyClass() replaces the ProxyFactory.classloaderProvider on any exception with a classloaderProvider that is very unlikely to work better than the default.  Setting the classLoaderProvider should be a matter of intentional configuration, not flailing around after an unexpected exception.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira