<properties> for annotations

Description

It is actually hard to find a good annotation representing such a grouping.
@Properties at the entity level is nasty but is the only one I can think of that fits all the needs.

Environment

None

Activity

Show:
Emmanuel Bernard
October 6, 2006, 8:34 PM

I'm concerned about the ordering.
Ordering matters in <properties>

Steve Ebersole
October 26, 2015, 4:11 PM

For what purpose?

Emmanuel Bernard
October 27, 2015, 1:17 PM

For what purpose?

If that's related to the ordering, here is my reasoning. The TestNG like feature does not keep around the fact that prop1 and before prop2 in the properties list.
My recollection of the ORM engine is that this ordering does matter one way or the other (same column order?). If I am wrong and that the order does not matter, then I like the TestNG approach (it makes things a bit difficult to read when you have hierarchy of classes but that's probably acceptable.

Steve Ebersole
October 27, 2015, 1:20 PM

No, I mean in what context in binding annotations do we care about the order of the properties/attributes?

Emmanuel Bernard
October 27, 2015, 1:31 PM

When using the reflection API in Java, you have no guaranteed order in which properties are returned. I don't know if Jandex offers any guarantee either.
So we only care if the underlying ORM mapping requires us to have a specific order.

Assignee

Unassigned

Reporter

Emmanuel Bernard

Fix versions

None

Labels

None

backPortable

None

Suitable for new contributors

None

Requires Release Note

None

Pull Request

None

backportDecision

None

Components

Priority

Blocker
Configure