On 05/27/2016 01:40 PM, Remi Forax wrote:
I don't see the issue if the lookup object represent the proxy class itself
restricted to only access to public methods.
Rémi
I think there could be security issues. For example, let there be an
interface like:
public interface Resource {
Inp
- Mail original -
> De: "Peter Levart"
> À: "Remi Forax" , "Da Vinci Machine Project"
>
> Cc: "jochen Theodorou"
> Envoyé: Jeudi 2 Juin 2016 10:26:48
> Objet: Re: proxy an interface and call a default method
>
>
>
> On 05/27/2016 01:40 PM, Remi Forax wrote:
> > I don't see the issu
Never-taken GWT branches (on per-MH instance basis) are aggressively
pruned during JIT-compilation.
So, in the worst case, a MH chain containing 6 GWT can experience 6
recompilations.
I don't know what Java version you use, but there were a number of bugs
fixed in HotSpot, which manifested a
Hi Remi, Jochen,
On 06/02/2016 11:15 AM, fo...@univ-mlv.fr wrote:
>The solution could be for Proxy API to provide a MH that was already
>bound to the Proxy instance. Such pre-bound MH could not be abused then.
independently of any security issue, it may be a good idea but doing a partial
eval
- Mail original -
> De: "Peter Levart"
> À: fo...@univ-mlv.fr
> Cc: "Da Vinci Machine Project" , "jochen
> Theodorou"
> Envoyé: Jeudi 2 Juin 2016 15:23:44
> Objet: Re: proxy an interface and call a default method
> Hi Remi, Jochen,
> On 06/02/2016 11:15 AM, fo...@univ-mlv.fr wrote:
>
