Hello Jessies,
I played with the Jess bsave/bload functions and have a few
questions/remarks:
1. a short note in the Jess function list documentation might be helpful
that the user needs
to declare the java.io.Serializable interface for all involved Java
beans (would have saved
me some time finding out myself :~)
2. I was a little disappointed about the performance - possibly this is
due to the
compression/decompression phase (?). If so, would it be possible to
add a way to
control this (may be a flag like (bsave <file> <boolean do-compress>)
or so?
3. After bloading the result I get errors I don't get when loading Jess
files normally.
They complain about non-overloadable methods blah blah.
My suspicion is that this is because my Java beans have for many
properties multiple set()
methods (declared in BeanInfo files). Works fine normally.
Example:
class bla {
int x = 0;
void setX(int v) { x = v; }
void setX(String v) { ... }
int getX() { return x; }
}
Looks as if the alternate set() methods are lost ... is that possible
(rather a Java
question, but maybe somebody knows)?
4. Since this uses some kind of standard Java serialization - is the
result portable across
different hardware/OS?
Thanks a lot,
tge
Thomas Gentsch
---------------------------------------------------------------------
To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]'
in the BODY of a message to [EMAIL PROTECTED], NOT to the
list (use your own address!) List problems? Notify [EMAIL PROTECTED]
---------------------------------------------------------------------
