<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 12px; font-family: Arial, sans-serif;">
<div>+1</div>
<div><br>
</div>
<div>(even though I can live with a portable alternative approach to the current PR)</div>
<div><br>
</div>
<div>So far I did not express my support for this PR even though I promised to do so. Unable to proxy those classes is a major issue to me while migrating old software to a newer environment.</div>
<div><br>
</div>
<div>As soon as you deal with 5 to 10+ years old software and try to migrate your large application step by step you will encounter framework base classes with (protected) final methods. CDI, @Inject and interceptors help a lot to cleanup the old stuff, however
I have to extend (currently unproxyable) framework base classes to do so. Example: I have to extend AbstractFrameworkXyzAction with public and/ or protected final methods to implement use case logic, and the derived classes should be CDI beans. </div>
<div><br>
</div>
<div>On the other hand - changing the old jar's is not an option either.</div>
<div><br>
</div>
<div>With this feature I can stop copying the modified base classes to my local archive (mostly .war) in order to override the old classes.</div>
<div><br>
</div>
<div>Jens</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">Von: </span><<a href="mailto:cdi-dev-bounces@lists.jboss.org">cdi-dev-bounces@lists.jboss.org</a>> on behalf of Antoine Sabot-Durand <<a href="mailto:antoine@sabot-durand.net">antoine@sabot-durand.net</a>><br>
<span style="font-weight:bold">Datum: </span>Tuesday 9 February 2016 17:36<br>
<span style="font-weight:bold">An: </span>CDI-Dev <<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a>><br>
<span style="font-weight:bold">Betreff: </span>[cdi-dev] [Vote] for CDI-527 / PR 271 allow proxying of classes with non-private final methods<br>
</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div>
<div dir="ltr">
<div>Hi all,</div>
<div><br>
</div>
<div>There have been a lot of discussion around CDI-527 in the last weeks:</div>
<div><a href="https://issues.jboss.org/browse/CDI-527">https://issues.jboss.org/browse/CDI-527</a><br>
</div>
<div><br>
</div>
<div>Mark proposed a PR:</div>
<div><a href="https://github.com/cdi-spec/cdi/pull/271">https://github.com/cdi-spec/cdi/pull/271</a><br>
</div>
<div><br>
</div>
<div>But we don't agree on adding this feature to the spec.</div>
<div>This vote is to decide if we should add this feature at the spec level now, or not.</div>
<div>Should we vote this feature down, that won't mean it will be completely dropped: it could be implemented as non portable feature in both Spec or even be included as experimental feature in the spec (in annexes) as describe in the PR comments</div>
<div>Vote starts now, only vote from EG members are binding (but you can give your opinion if not part of the EG) and will last 72 hours.</div>
<div><br>
</div>
<div>You vote with the following values:</div>
<div>+1 : I'm favorable for adding this feature in the spec<br>
</div>
<div>-1 : I'm against adding this feature in the spec</div>
<div>0 : I don't care</div>
<div><br>
</div>
<div>Thank you for your attention and your vote.</div>
<div><br>
</div>
<div>Antoine Sabot-Durand</div>
</div>
</div>
</div>
</blockquote>
</span>
</body>
</html>