Entity Listener

[gtsluk]

@Entity(value = "entity", useDiscriminator = false)
@EntityListeners(FieldSigner.class)
public class Entity Aextends RootDocument {
    private String name;
    @EncryptedField
    private String businessEmail;
}

@Target({ElementType.FIELD, ElementType.TYPE})
@Retention(RetentionPolicy.RUNTIME)
public @interface EncryptedField {
}

@Singleton
@Startup
public class FieldSigner {
    @PrePersist
    void prePersist(Object entity) throws IllegalAccessException {}
    @PostLoad
    void onPostLoad( Object entity ) throws IllegalAccessException {
}

The signer class may be triggered when the entity register in morphia lifeCycle decoder. Are there any properties ensure the entity class being mapped in the lifeCycleDeoced?

[evanchooly]

I'm not sure I understand your question. Could you elaborate?

[gtsluk]

we're using

dev.morphia.morphia
morphia-core
2.2.6

[evanchooly]

If you're using quarkus then configure it via application.properties.

[gtsluk]

we use the Morphia core library rather than QUARKUS-MORPHIA. Therefore, the solution is stored the package name in the form of comma-separated in the application properties and called morphia.mapPackage() after creating the morphia. Please correct me if I moved in the wrong direction.

[evanchooly]

So is this a quarkus app or no? It feels like we've gone back and forth on the point. If it's a quarkus app, you really should use quarkus-morphia and application.properties to make sure you take advantage of the work that the extension will (eventually) do for you. But if you list the packages in application.properties, there is no need to call mapPackage() as the extension will do that for you.

On the other hand, there's nothing wrong with using Morphia directly. You just won't get any build time support and probably native mode will break on you if that's a thing you care about. Not everyone does.

[gtsluk]

It is a Quarkus app. But I found the eventListener eventually works on OpenShift.