What would be the alternative to active objects in jira plugin development? -

this issue here says trasnactions don't work in jira.

i guess means active objects useless, , unusable in production environment.

so alternative?

i'm new jira plugin development, , i'm working on first project, doing java backend part. had hard time getting active objects stuff work, , spent(wasted?) week on it.

i need full database support, moving key-value pair system not enough.

any appreciated.

edit, trying clarify:

i'm creating plugin jira, enables track users time logging. want save users input of worktime data, , show in meaningful way.

(warning) please note, jira not support transactions active objects (as of jira 6.0).

public void somemethod(final activeobjects ao) {     ao.executeintransaction(new transactioncallback<object>()     {         @override         public object dointransaction()         {             // ao. according docs, not run in transaction.             return null;         }     }); } 

so if still want use dbs in jira, alternative active objects? far know, databases without transactions make no sense.

cross posted...

i choose jdbctemplate, ao used create table