You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add methods to XQConnection2 to enable the user to specify their own XQCommonHandler implementation in such a way that they can also simply override certain scenarios (e.g. certain Objects) and allow the rest of the XQJ driver to cater for everything else, as it would do normally.
So essentially, the user could create an implementation, something along the lines of:
Create
XQCommonHandler
interface, along the lines of:Add methods to
XQConnection2
to enable the user to specify their ownXQCommonHandler
implementation in such a way that they can also simply override certain scenarios (e.g. certain Objects) and allow the rest of the XQJ driver to cater for everything else, as it would do normally.So essentially, the user could create an implementation, something along the lines of:
When a user is using a custom
XQCommonHandler
, methods such asXQItemAccessor.getObject()
XQDynamicContext.bindObject(QName varName, Object value, XQItemType type)
XQDataFactory.createItemFromObject(Object value, XQItemType type)
will be affected.
This must be well documented.
The text was updated successfully, but these errors were encountered: