Craig -
Thanks for the info. Following further research, I think I've found the docs you
referred to below... my apologies for not employing the bionic eye. Anyway, according
to your suggestions, and what I've gathered from the docs/examples, I think I've made
the appropriate changes, though the app persists to malfunction in an interesting
manner.
The .wod is now:
// *** PhoneNumbers.wod
PhoneNames: WOPopUpButton {
displayString = aPhone.Name;
item = aPhone;
selection = selectedPhone;
list = phoneNumberDisplayGroup;
}
PhoneNumber: WOTextField {
value = selectedPhone.Number;
}
UpdateButton: WOSubmitButton {
action = updateView;
value = "Update View";
}
and .java is now:
// *** PhoneNumbers.java
public void updateView() {
System.out.println("In updateView...");
System.out.println(
"phoneNumberDisplayGroup.selectedObject() -> " +
phoneNumberDisplayGroup.selectedObject());
System.out.println(
"selectedPhone -> " + selectedPhone);
phoneNumberDisplayGroup.selectObject(selectedPhone);
System.out.println(
"phoneNumberDisplayGroup.selectedObject() -> " +
phoneNumberDisplayGroup.selectedObject());
}
The new (erroneous) behavior is this...
The page loads, and the popup is populated w/ the appropriate "name attributes" of the
PhoneNumber(s) in the display group. However, the text fields associated w/
selectedPhone are all empty. Further, when I choose "Update View", the System.out(s)
yield the following:
In updateView...
phoneNumberDisplayGroup.selectedObject() -> {
self = "<PhoneNumber[PhoneNumber](0xaf1150)>";
values = {AreaCode = 425; Extension = 43007; Name = Office; Number = ***.9447; };
}
selectedPhone -> {
self = "<PhoneNumber[PhoneNumber](0xaf1d50)>";
values = {AreaCode = <null>; Extension = <null>; Name = <null>; Number = <null>;
};
}
phoneNumberDisplayGroup.selectedObject() -> {
self = "<PhoneNumber[PhoneNumber](0xaf1d50)>";
values = {AreaCode = <null>; Extension = <null>; Name = <null>; Number = <null>;
};
}
As can be seen, although the display group reports a selected object, the text fields
were blank; I'm assuming that when the popup is displayed, there is - by default - no
object chosen as the selection, which would explain the blanks. However, w/in update
view, selectedPhone should be equal to the popup's selection attribute; instead the
object being returned is all nulls. Consequently, when the selected object of the
display group is set to be the selectedPhone, the entry in the display group is
"nulled" out. The end result that no matter what object I choose from the popup, if I
continue attempts to update the view, all the display group entries are "blanked out"
one by one. Neat functionality, isn't it?
Looking forward to a slap in the face when I learn how easy the solution is... any
takers?
And that's one of the great things about Seattle; I never need fret about the fact
that I might rather go outside and play rather than slaving away on WebObjects...
'cause I always no it'll rain again tomorrow. :)
tia
mx.
Michael G Xenakis PLATINUM technology, inc
[EMAIL PROTECTED] 800.365.7528 x43007
"Anyone who isn't confused here doesn't really understand what's going on!"
