[
https://issues.apache.org/jira/browse/PROXY-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12576754#action_12576754
]
James Carman commented on PROXY-11:
-----------------------------------
So, you're saying we should add in a discovery mechanism similar to JCL? So,
how does Commons Proxy decide which implementation is "better"? In a
HiveMind/Hibernate environment, which would include both Javassist and CGLIB
(and the JDK of course :), which one would it choose? If we're going to do
anything at all, I think it would be a wiser choice to go with the SLF4J route
and let the client project choose the implementation it prefers by including
the implementation-specific jar in the classpath. Otherwise, we have to build
in a way to override the default choosing algorithm with a properties file or
something. Changing the build wouldn't really be that difficult as far as
Maven is concerned.
> slf4j-like discovery of the Proxy implementation to use
> -------------------------------------------------------
>
> Key: PROXY-11
> URL: https://issues.apache.org/jira/browse/PROXY-11
> Project: Commons Proxy
> Issue Type: Improvement
> Affects Versions: 1.0
> Environment: wicket
> Reporter: Johan Compagner
>
> I set this prio to major but for wicket it is really a blocker. In the
> current state i just cant use commons proxy
> I dont want in a general framework to make a decission which implementation
> that i should use
> Something like this should be done outside the code or at least outside my
> code (that slf4j or commons logging also do)
> Look at how slf4j does it because the commons logging way is a bit flawed
> (classloading problems)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
