Updating db property

Support
#1

I am trying to update a db property and it is not working, only works the first time, when it does not exist in database.

This is the method I use to store it:

@Property("comprob.fechaerrpedidb")
void setFechaErrPediDB(String fecha);

Thanks in advance

#2

Do you have a corresponding getter?
How did you define it?
How did you check that the value is not stored?

#3

This is the interface I have defined:

@Source(type = SourceType.DATABASE)
public interface ComprobConfigDB extends Config {

    @Property("comprob.fechaerrpedidb")
    String getFechaErrPediDB();

    @Property("comprob.fechaerrpedidb")
    void setFechaErrPediDB(String fecha);

}

Here is where I try to store it and check if it is done:

public void modificarFechaPasadaErrpedi(String horaAhora){
   comprobConfigDB.setFechaErrPediDB(horaAhora);

   if(comprobConfigDB.getFechaErrPediDB().compareTo(horaAhora) == 0 ){
        System.out.println("Fecha base de datos guardada " + horaAhora);
   } else {
       System.out.println("Fecha base de datos no guardada " + horaAhora);
   }
}
#4

We normally define @Property annotation on the getter only. The setter is found automatically by its name. Please try to remove it from setter, and check the saving again.

#5

Now works sometimes locally but not in production server, what can I do?

#6

Do you mean it works after removing the second @Property annotation?

Where does your code checking the value works, on the middleware or on the client?

#7

It works three/four times and then it does not update it.

I check it in a service bean.

#8

Please check if the new value is saved by using App Properties screen or ConfigStorage JMX bean. When you check in the same service method that modifies the property, it may depend on how you use transactions in your service. The setProperty method works in the same transaction as the calling code (if there is an active transaction), while the getProperty method reads the properties cache always in a new transaction, so it may not see the changes.

#9

Now it is working perfectly in my local server, but in production server setProperty is storing property well and getProperty is reading sometimes the last value saved before actual value