Hi,<div><br></div><div>Did you already had a change to think about #224?</div><div>Sorry for the bump but its very important for me ;)</div><div><br></div><div>Regards,</div><div>Thomas<br><br>Am Freitag, 17. Oktober 2014 schrieb Thomas Andraschko :<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div><div><div><div><div>Hi,<br><br></div>we have a big product with many subproducts/projects and customizations for some customers.<br></div>CDI and JSF is really doing a great job here but i found 2 really annoying issues which could be improved:<br></div><br>- CDI-224: Allow decoration on classes, not only on interfaces<br></div> <br> We created many interfaces the last months for our beans just to get decoration working<br></div> This is really annoying as this interfaces are just overhead and actually senseless for us.<br><br><br></div>- CDI-407: Specify @Named @Alternatives<br></div> <br> Currently its not defined what should happen if a alternative has a @Named and is activated via beans.xml in the current app:<br><br></div><div> @Named public class A<br> @Named @Alternative public class B extends A<br><br></div><div> or even something like:<br><br> @Named public class A<br> @Specializes public class B extends A<br> @Named @Alternative public class B2 extends B</div><div> <br> IMO B and B2 should also be available via EL "a".<br><br><br><br></div>This are really important issues for standard cases.<br>It would be great to see it in CDI 2.0.<br><br></div>Best regards,<br>Thomas<br><div><div><div> <br></div></div></div></div>
</blockquote></div>