Thanks Rob.
In fact I decided to get to the bottom of the problem, and i did as far as I
need to.
When I design any new stuff I try to avoid the Studio stuff except for
vanila single-table-maintenance pages, but that is not the case when you are
working on something inherited from somebody.
I had a page with a mind-boggling number of fields and there used to be 'n'
number of that stupid message. I tried to simulate the error with a bound
displayfield fed with null values, without success.
Finally I identified those fields which were causing this problem.
Here's my conclusion:
Any ComboBox whose 'values' are numeric, when bound to a datafield is a
potential candidate. If the datafield value happens to be null at run-time,
ND tries to pull a longValue() from the CSpNull and throws this dump error -
not once, not twice, but *once for each element in the comboBox* - if your
comboBox has 50 elements, you get 50 of these messages for free!
Having made this diagnosis, what I thought the easiest fix was to subclass
CSpComboBox.
==========================================================
public class PuCSpComboBox extends CSpComboBox
{
public PuCSpComboBox () {
super();
}
public boolean select(CSpValue value, boolean refreshPeer) {
if (!value.isNull())
return super.select(value, refreshPeer);
else
return true;
}
}
==========================================================
That works great so far.
Aby
-----Original Message-----
From: Archambault, Robert [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 28, 1999 7:15 PM
To: 'Aby Mathew'; 'ND4'
Subject: RE: [ND] 'spider.session.CSpNull' has not implemented this
method
Aby,
I have seen this issue when a null field from the database is being bound to
a display field on the page. Both times I have seen it, it was binding via
the studio rather than manually binding the fields in the Java code.
The resolution was to remove the 'automated' binding that the studio was
doing and manually binding the fields in the Java code while looking to see
if the value is null before setting the display field.
Hope this helps.
Let me know if you have any questions.
Rob
-----Original Message-----
From: Aby Mathew [SMTP:[EMAIL PROTECTED]]
Sent: Tuesday, October 26, 1999 8:17 PM
To: 'ND4'
Subject: [ND] 'spider.session.CSpNull' has not implemented
this method
Hi all,
This is the worst hiccup we have been having ever since we converted
from
ND3 to ND4. Certain pages in the application keeps throwing the
following
error:
============================================================================
========
551 Oct 26, 1999 at 16:57:32.677 Warning Thread-69
CPService
spider.session.CSpNull:c:940874284239:w:940874284728:longValue: The
CSpValue
derived class 'spider.session.CSpNull' has not implemented this
method
============================================================================
========
This is something that went down in priority, due to the other
fire-fighting
that was going on, but it looks really nasty when this message fills
up the
log in the production server.
No, there is no attempt to pull out "longValue()" anywhere in the
code, it
can only be happening with some bound fields and some implicit stuff
ND is
doing for me.
My frustration level occassionally rises to the extend of thinking
about
de-compiling CSpNull.class and implementing longValue(). (Not sure
if Sun
will reward me or sue me!)
If anybody has a clear hint pls let me know.
Thanks in advance.
Aby Mathew
_________________________________________________________________________
For help in using, subscribing, and unsubscribing to the discussion
forums, please go to:
http://www.netdynamics.com/support/visitdevfor.html
For dire need help, email: [EMAIL PROTECTED]
_________________________________________________________________________
For help in using, subscribing, and unsubscribing to the discussion
forums, please go to: http://www.netdynamics.com/support/visitdevfor.html
For dire need help, email: [EMAIL PROTECTED]
