Alternative suggestions to creating a TransactionEventHandler for UID generation?

[Stacy Tyler Young]

I'm using a TransactionEventHandler to generate a UID for entities (to avoid using graph id) but doing so in the transaction has its drawbacks. For one, if you're using @Transactional on a method the UID property value is not accessible within said method. I'd rather not start dropping txn boilerplate code into my classes ...anyone have an alternative approach?

[Michael Hunger]

Stacy,

can you raise a JIRA issue for that ?
In general I think it would be sensible to have a callback mechanism at "save()" instead of relying on the lower-level tx handlers of Neo4j.

Michael

Am 18.08.2012 um 00:06 schrieb Stacy Tyler Young:

> I'm using a TransactionEventHandler to generate a UID for entities (to avoid using graph id) but doing so in the transaction has its drawbacks. For one, if you're using @Transactional on a method the UID property value is not accessible within said method. I'd rather not start dropping txn boilerplate code into my classes ...anyone have an alternative approach?
>

> --
>
>

[Stacy Tyler Young]

What would you say to an even more direct approach to satisfying this use case. Perhaps an annotation to indicate a) unique key must be generated and b) implementation of generator class for said key?

Stacy

--

[Stacy Tyler Young]

Maybe even just an additional option on @Indexed?

[Michael Hunger]

Yep, that is another thing I'd like to add.

Michael

Please raise a JIRA issue for those 2 things.

--