Channels
#spring
- m
masted
05/06/2016, 7:42 AMIt is the main question. 😆 It is the first "reason" and the assumption to the initial question about reasons to not use. - s
sdeleuze
05/06/2016, 7:44 AMWhat I have in mind is using post-compile weaving - s
sdeleuze
05/06/2016, 7:45 AMThat could maybe allow to deal with bytecode generated by Kotlin compiler - s
sdeleuze
05/06/2016, 7:46 AMBut again I am really not an Aspect guru (if I was, I would have think about that first) so better to wait Juergen feedback - s
sdeleuze
05/06/2016, 7:48 AMI guess there will be also some tooling issue around incremental compilation, but that could be improved I guess - d
dh44t
05/06/2016, 9:26 AMMy humble opinion here: Kotlin features outweigh the
pain. In most cases will be needed just in configuration classes (from a Spring perspective, other frameworks could vary)open - s
sdeleuze
05/06/2016, 12:49 PM@dh44t: if is not only @Configuration but also most @Service and @Repository - d
dh44t
05/06/2016, 12:50 PMok - d
dh44t
05/06/2016, 12:53 PMI tend to don’t use to much magic in those layers - s
sdeleuze
05/06/2016, 12:55 PM@Transactional, Spring Security and even just exception mapping require proxies - m
masted
05/06/2016, 1:05 PMBtw, is the problem still there if each of
or@Service
has an interface that defined explicitly?@Repository - d
dh44t
05/06/2016, 1:05 PMNot if you use interfaces - m
masted
05/06/2016, 1:06 PM😆 - d
dh44t
05/06/2016, 1:06 PMor at least that’s the theory - d
dh44t
05/06/2016, 1:07 PMthe proxy should wrap around your class without extending it - m
masted
05/06/2016, 1:07 PMAccording to the spec the jdk proxy appears in such case yea. - d
dh44t
05/06/2016, 1:08 PMis a good practice anyway - s
sdeleuze
05/06/2016, 3:44 PMEven with interfaces Spring Boot use cglib for exception mapping - d
dh44t
05/06/2016, 9:21 PMhmm - d
dh44t
05/06/2016, 9:21 PMok - d
dh44t
05/06/2016, 9:21 PMthat’s different - h
hhariri
05/07/2016, 11:14 AMJust as a FYI, in the C# world, everything must have an interface purely for the purpose of IoC or mocking. - d
dh44t
05/07/2016, 12:15 PMis a good practice - d
dh44t
05/07/2016, 12:15 PMeasy to test, open opportunity to useful patterns - d
dh44t
05/07/2016, 12:20 PMas I said before, Kotlin features outweigh the need to open some classes - d
dh44t
05/07/2016, 12:21 PMI’ll like the idea of `allopen`or something similar not just for Spring but for other frameworks too - h
hhariri
05/07/2016, 2:27 PM@dh44t: well, being good practice is somewhat relative no? Introducing an interface that’s not needed other than for testing... - h
hhariri
05/07/2016, 2:28 PMwhich then leads to the patterns we have of naming. In Java -> Service, ServiceImpl. In C# IService, Service - d
dh44t
05/07/2016, 2:33 PMisn’t just for testing but for evolving and changing implementations - d
dh44t
05/07/2016, 2:34 PMparticularly with Spring you could split your normal app into a fully distributed with no changes on code just by configuration changes and Spring Remoting