[
https://issues.apache.org/jira/browse/OWB-496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12997613#comment-12997613
]
David Jencks commented on OWB-496:
----------------------------------
I don't think anyone has tried to explain why its a good idea to flail around
with unexpected exceptions rather than installing a classloader provider that
is suitable for the environment OWB is running in.
I hope you don't synchronize a static or singleton method that is called very
frequently from multiple threads. I think that would be required to make this
exception handling code work.
> 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
