Currently, recent modifications have regressed to just the former. Latter logic is no longer working.

It is all based on the parsing of the mappedBy annotation field and the determination of whether to instantiate ObjectReferenceDescriptor or OwningObjectReferenceDescriptor.

Former logic operated as follows:

If mappedBy = "" then instantiate ObjectReferenceDescriptor.
If mappedBy= "something" then drill into class reflection and find the owner and it's associated property and instantiate OwningObjectReferenceDescriptor using those attributes retrieved from class reflection.

Kenneth William Colassi
added a comment - 30/Aug/07 10:35 AM STATUS...
I had dropped the ball on this since it's creation.
The past 4 weeks have been hampered with ognl breakages and running the trails app has been close to impossible.
Couple that with pre-emptions and there is not alot I have been able to reliably do with regard to operating this functionality (that being the OneToOne editor).
I would like to resume and fix this unless someone has a better in to the code than I do.
This bug basically requires that the OneToOne editor be re-looked-at and resolved since it was breaking after the tapestry-4.1.2 merge.

Kenneth William Colassi
added a comment - 11/Sep/07 2:26 PM Ok, the new behavior of this editor currently is the following asof current checkins:
Click NEW on the OneToOne property (ie. and nothing happens.
no editor comes up
editor page blips/blinks
no behavior whatsoever

Although soft associations by AssociationSelect may have been mentioned, impacted and subsequently resolved throughout the framework, the main initiative behind this JIRA was the impact to hard associations implemented by the OneToOne property editor. They got broken post T-4.1 merge.

The semantics surrounding the descriptor decorator are under review.

The main problem is that the case logic currently is resulting in the wrong desciptor being allocated at bootstrap.

Kenneth William Colassi
added a comment - 12/Sep/07 12:31 PM Needed to clarify the title to this...
Although soft associations by AssociationSelect may have been mentioned, impacted and subsequently resolved throughout the framework, the main initiative behind this JIRA was the impact to hard associations implemented by the OneToOne property editor. They got broken post T-4.1 merge.
The semantics surrounding the descriptor decorator are under review.
The main problem is that the case logic currently is resulting in the wrong desciptor being allocated at bootstrap.

Originally I designed this to operate the @OneToOne attribute mappedBy which gave us a handle to the inverse that the developer codes to the class.

This design has changed and I decided to go with the extra annotation @HardOneToOne for detection/isolation of logic. I would have preferred to instrument @OneToOne with Identity but was discouraged from that.

For your pojos...
To setup the hard owner we use two annotations
@OneToOne
@HardOneToOne(identity = Identity.OWNER)
To setup the hard association we use two annotations
@OneToOne
@HardOneToOne(identity = Identity.ASSOCIATION)