just wondering why it is giving this warning

hmm, ok I double checked, same kind on warning occurs for a similar Java class

so this seems to have nothing to do with kotlin

>>@Service

public class MyClass { @Cacheable public void public_method__OK() {} public final void public_method__WARNING_OK() {} private final void private_method__WARNING_WHY() {} private void private_method__OK() {} }

@deckard_shaw has left the channel

Hi all 🙂 We've just open-sourced a Kotlin DSL for Spring Data JPA (i.e. type-safe criteria queries). Feedback welcome! https://github.com/consoleau/kotlin-jpa-specification-dsl

@james_bassett That looks pretty amazing. I’ll have to check it out.

@dh44t i can't handle transactions manualy ?

like this :

fun myTransactionalFunction() = session.transaction { }

@dimitar_ has left the channel

yes, you could

but @Transacational is easier

of you use session in your service layer you’re mixing your data access logic into your service layer

if i use interface how kotlin allows to spring that proxy this functions ?

‘cause Kotlin interfaces are plain Java Interfaces

It's mean that kotlin interfaces are not final ?

you need to put open on everything ‘cause the Spring proxy mechanism is trying to extend your type with the proxy

if you, in Java or Kotlin, use an interface, Spring could use your type, the interface in this case, and doesn’t need to extend your class

thanks, alot.

test it, please

But i must be generate lot's of interfaces and it's boring.

yep

I like interfaces anyway, are easier for testing

to define a function in two files.

there are some tickets on YouTrack to relax this behaviour for proxy dependent frameworks

Yes should be fixed in Kotlin 1.1

@sdeleuze you mean https://github.com/Kotlin/KEEP/pull/40 ? is there already an agreement what the "fix" should be? to me it seems like there are still a few things to decide

I have no official statement but from the discussion we had Kotlin 1.1 is expected to fix that. I will ask a confirmation on the PR.

Has anyone had problems with mapping JSON to a parameter like

@RequestBody data: MyClass

? I experience a weird behaviour of Spring: when number and order of properties in the sent JSON doesn’t match those in

MyClass

, the mapper loses some values.