|
Sort Order:
Here is the trails-core patch file. Here is the trails project roster example patch file Here is my version of the example POM... Latest Patch file attached uses re-vamped AssociationCallback with instrumented OGNL. Association still fails to stick. Cannot get the association to stick outside of this OneToOne editor either. If I focus on instance editor for the association alone, it fails to stick there either. Thinking it surrounds the AssociationSelect widget but getValue/setValue are being propagated in/out of that widget for the association property. This can't be a Cascade issue can it ? Will someone please look at this amd provide comment/input? Thanks |
|||||||||||||||||||||||||||||||||||||||||||
New Feature
Closed
Major
@OneToOne needs user interface semantics
Attached is a prototype that successfully implements front end for a hard OneToOne association.
There is a bug though. The OneToOne association in the back end is not sticking. A test was successfully performed that validates the mappings are working on hibernate. OGNL was implemented to sustain the inverse property of the OwningObjectReferenceDescriptor. This stick issue still persists.