Jerome Said:
I don't think this is the right way of doing this. the model is
capable
of maintaining its own integrity (of course, if you modify the
domain.xml manually, you are on your own).
By using the reference() feature of the @Element annotation, we would
ensure that the config always exist.
Byron Asks:
I made the change -- the checking code now logs a warning instead of
throwing an Exception. An Exception is never thrown when there is a
config element missing.
How does the above "reference() feature" work? Do I need to do
something or is it already in-place and automatic?
Is this referential integrity verified when the server element is
created and/or saved?
On 3/19/2010 9:58 PM, Byron Nevins wrote:
I don't
think this is the right way of doing this. the model is capable
of maintaining its own integrity (of course, if you modify the
domain.xml manually, you are on your own).
By using the reference() feature of the @Element annotation, we would
ensure that the config always exist.
--
Byron Nevins - Sun Microsystems, Inc.
Home: 650-359-1290
Cell: 650-784-4123
Sierra: 209-295-2188