I think the problem is here:
if (sourceDataBinding == null || targetDataBinding == null
|| !sourceDataBinding.equals(targetDataBinding)) {
The databinding interceptor should not be interposed if the
databindings are undefined.
Jim
On Jan 2, 2007, at 11:26 AM, Raymond Feng wrote:
Hi,
I think we have some checks (test if the databindings are equal for
source and target operations) before adding the interceptor. This
might not be fully optimized.
Thanks,
Raymond
----- Original Message ----- From: "Jim Marino"
<[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Tuesday, January 02, 2007 11:18 AM
Subject: Databinding interceptor
Raymond, maybe you could answer this...
I've noticed that the Databinding interceptor seems to be getting
added to all wires, regardless of whether it is needed or not. Is
this correct? If so, we should change the behavior of the post
processor to only add the interceptor when needed, otherwise we
will not be able to optimize wires (and also avoid the overhead
of an additional method call).
Jim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
