Add support of @Sql in tests of @ApplicationModuleListener

[yerzhant]

Could you please add support of sql scripts in tests of module listeners (org.springframework.modulith.events.ApplicationModuleListener)?

I. e. this:

    @Test
    @Sql("classpath:sql/some-inserts.sql", "classpath:sql/file-abcd.sql")

do inserts rows in one transaction, but this:

    @ApplicationModuleListener
    fun on(event: SomeCoolStuffHappened) {

creates a new txn and does not see inserts from @Sql. W/o this support one need to mock a bunch of stuff.

Thanks in advance!

[odrotbohm]

Can you provide a minimal reproducer (ideally Java, Maven) that shows what's not working? I would expect the code behind @Sql to commit the changes and fully execute before a test method is invoked, so that the database content should be visible to new transactions.

[yerzhant]

It does work but, as was said higher, it creates a new transaction and does not see what a script in @Sql has done.

Could you please remove a requirement to create a new transaction on every call of @ApplicationModuleListener method? As a consequence the listener doesn't see what had been done in @Sql and it prevents one from calling a listener from an existing transaction so that what happens in the listener must be a part of some "larger/wider" work.

One even can't do like this to override propagation level:

    @ApplicationModuleListener
    @Transactional(propagation = REQUIRED)
    fun on(event: IndividualUpdated) {

It would be great if the annotation will be like:

@Async
@Transactional(propagation = Propagation.REQUIRED)
@TransactionalEventListener
@Documented
@Target({ ElementType.METHOD, ElementType.ANNOTATION_TYPE })
@Retention(RetentionPolicy.RUNTIME)
public @interface ApplicationModuleListener {