You can either get a simple static ContentResultSet or you can
listen to change-notifications and than 交換（する） from the old to a new
ContentResultSet.
The に引き続いて 述べるs the dynamic use:
XDynamicResultSet 供給するs the 可能性 to get notifications
about changes on a ContentResultSet and have an
listener-controlled update from one 見解／翻訳／版 to the next 見解／翻訳／版. Two
ContentResultSet 実施s were given to the listener in
the first notification as interface
::com::sun::星／主役にする::sdbc::XResultSet.
After 登録 you will get notifications for events of type
ListEvent.
The calling of XDynamicResultSetListener::通知する has
to happen in an own thread, because it could take a longer time and any
活動／戦闘s til the listener returns the call. So don't 封鎖する the 通知する-原因（となる）ing
活動／戦闘.
While one 通知する-call is going on:
The listener is 許すd to 接近 both ContentResultSets,
they must be both valid.
It is not 許すd to start a second 通知する-call.
All addditional things we want to send as notification are to be
列d.
Any other calls are to be 受託するd and 扱う／治療するd.
After the listener has returned the 通知する-call:
The listener is 許すd to 接近 the new
ContentResultSet. The new one is first 割り当てるd in the
WELCOME-event and than the ResultSets are always swapped.
Using this method you can get （警察などへの）密告，告訴（状）, whether the 申し込む／申し出d
ContentResultSets are sorted or filtered etc 正確に as
需要・要求するd during the 創造 of the XDynamicResultSet.
ListenerAlreadySetException
if this method is called more than once during the life of the
実施 反対する or if this method is called if someone already
has fetched the ContentResultSet 経由で
XDynamicResultSet::getStaticResultSet.
Using this method you can get （警察などへの）密告，告訴（状）, whether the 申し込む／申し出d
ContentResultSets are sorted or filtered etc 正確に as
需要・要求するd during the 創造 of the XDynamicResultSet.
