Date
|
Description
|
Status
|
11/18/2003
|
stec.pos.ObjectStoreEnumeration.close() throws an
exception when stec.pos.ObjectStoreEnumeration.nextElement()
throws a TimeoutException.
This problem has been resolved in version 1.3.1
11/26/2003.
|
Fixed
|
11/18/2003
|
stec.xpos.ObjectStoreEnumeration.close() throws an
exception when stec.xpos.ObjectStoreEnumeration.nextElement()
throws a TimeoutException.
This problem has been resolved in version 1.3.1
11/26/2003.
|
Fixed
|
06/02/2003
|
stec.pos.CheckIndex does not correcly count duplicate
values.
This problem has been resolved in version 1.2.4
07/06/2003.
|
Fixed
|
06/02/2003
|
stec.xpos.CheckIndex does not correcly count duplicate
values.
This problem has been resolved in version 1.2.4
07/06/2003.
|
Fixed
|
06/02/2003
|
stec.pos.CheckIndex does not correcly count null
keys.
This problem has been resolved in version 1.2.4
07/06/2003.
|
Fixed
|
06/02/2003
|
stec.xpos.CheckIndex does not correcly count null
keys.
This problem has been resolved in version 1.2.4
07/06/2003.
|
Fixed
|
03/10/2003
|
java.io.File.getCanonicalPath() does not return
unique file paths.
Replaced use of java.io.File.getCanonicalPath() with
stec.io.File.getCanonicalPath() which returns unique
file paths.
|
Info
|
03/10/2003
|
Indexes throw java.lang.NullPointerException in
stec.pos.IndexInstance.check_value() when duplicates
was set to false.
This problem has been resolved in version 1.2.3
03/11/2003.
|
Fixed
|
03/10/2003
|
Indexes throw java.lang.NullPointerException in
stec.xpos.IndexInstance.check_value() when duplicates
was set to false.
This problem has been resolved in version 1.2.3
03/11/2003.
|
Fixed
|
02/28/2003
|
Any serializable object can be stored as a key by
specifying java.io.Serializable for the keys class
name.
Also, any serializable object can be stored as a
value by specifying java.io.Serializable for the
values class name.
|
Info
|
02/27/2003
|
Indexes did not properly store null keys and values.
This problem has been resolved in version 1.2.2
03/03/2003.
|
Fixed
|
02/25/2003
|
stec.pos.ObjectStore.create() did not delete all the
physical files when the object store was overwritten.
This problem has been resolved in version 1.2.2
03/03/2003.
|
Fixed
|
02/25/2003
|
stec.xpos.ObjectStore.create() did not delete all the
physical files when the object store was overwritten.
This problem has been resolved in version 1.2.2
03/03/2003.
|
Fixed
|
02/25/2003
|
stec.pos.Index.create() did not delete all the
physical files when the index was overwritten.
This problem has been resolved in version 1.2.2
03/03/2003.
|
Fixed
|
02/25/2003
|
stec.xpos.Index.create() did not delete all the
physical files when the index was overwritten.
This problem has been resolved in version 1.2.2
03/03/2003.
|
Fixed
|
02/21/2003
|
stec.pos.IndexedObjectStore.delete() did not delete
all the physical files when an existing indexed
object store was deleted.
This problem has been resolved in version 1.2.2
03/03/2003.
|
Fixed
|
02/21/2003
|
stec.xpos.IndexedObjectStore.delete() did not delete
all the physical files when an existing indexed
object store was deleted.
This problem has been resolved in version 1.2.2
03/03/2003.
|
Fixed
|
02/19/2003
|
stec.pos.IndexedObjectStore.removeIndex() did not
delete all the physical files when an existing index
was delete from the specified indexed object store.
This problem has been resolved in version 1.2.2
03/03/2003.
|
Fixed
|
02/19/2003
|
stec.xpos.IndexedObjectStore.removeIndex() did not
delete all the physical files when an existing index
was delete from the specified indexed object store.
This problem has been resolved in version 1.2.2
03/03/2003.
|
Fixed
|
02/18/2003
|
stec.pos.IndexReference.clear() did not clear all the
associated files.
This problem has been resolved in version 1.2.2
03/03/2003.
|
Fixed
|
02/18/2003
|
stec.xpos.IndexReference.clear() did not clear all
the associated files.
This problem has been resolved in version 1.2.2
03/03/2003.
|
Fixed
|
02/18/2003
|
stec.pos.IndexedObjectStoreReference.clear() did not
clear all the associated files.
This problem has been resolved in version 1.2.2
03/03/2003.
|
Fixed
|
02/18/2003
|
stec.xpos.IndexedObjectStoreReference.clear() did not
clear all the associated files.
This problem has been resolved in version 1.2.2
03/03/2003.
|
Fixed
|
02/14/2003
|
The root cause for an exception are not always being
propagated.
This problem has been resolved in version 1.2.2
03/03/2003.
|
Fixed
|
02/12/2003
|
stec.pos.Locker does not release all the locks when the
associated reference is closed or when unlockAll() is
used.
This problem has been resolved in version 1.2.2
03/03/2003.
|
Fixed
|
02/10/2003
|
stec.pos.ObjectStoreReference.getWhoLocked() does not
check whether the reference is stil opened.
This problem has been resolved in version 1.2.2
03/03/2003.
|
Fixed
|
02/10/2003
|
stec.xpos.ObjectStoreReference.getWhoLocked() does not
check whether the reference is stil opened.
This problem has been resolved in version 1.2.2
03/03/2003.
|
Fixed
|
02/10/2003
|
stec.pos.IndexReference.getWhoLocked() does not check
whether the reference is stil opened.
This problem has been resolved in version 1.2.2
03/03/2003.
|
Fixed
|
02/10/2003
|
stec.xpos.IndexReference.getWhoLocked() does not check
whether the reference is stil opened.
This problem has been resolved in version 1.2.2
03/03/2003.
|
Fixed
|
02/06/2003
|
stec.pos.IndexedObjectStore.delete() allows the
indexed object store to be deleted when it is in use.
This problem has been resolved in version 1.2.2
03/03/2003.
|
Fixed
|
02/06/2003
|
stec.xpos.IndexedObjectStore.delete() allows the
indexed object store to be deleted when it is in use.
This problem has been resolved in version 1.2.2
03/03/2003.
|
Fixed
|
02/05/2003
|
stec.pos.IndexedObjectStoreReference.contains() did
not properly compare values.
This problem has been resolved in version 1.2.2
03/03/2003.
|
Fixed
|
02/05/2003
|
stec.xpos.IndexedObjectStoreReference.contains() did
not properly compare values.
This problem has been resolved in version 1.2.2
03/03/2003.
|
Fixed
|
02/03/2003
|
stec.pos.Index.expand() does not properly expand
associated files.
This problem has been resolved in version 1.2.2
03/03/2003.
|
Fixed
|
02/03/2003
|
stec.xpos.Index.expand() does not properly expand
associated files.
This problem has been resolved in version 1.2.2
03/03/2003.
|
Fixed
|
12/20/2002
|
stec.pos.Index.create() improperly sets the keys
index file's length when a fixed number of keys
index pages was specified.
This problem has been resolved in version 1.2.1
12/22/2002.
|
Fixed
|
12/20/2002
|
stec.pos.Index.create() improperly sets the values
index file's length when a fixed number of values
index pages was specified.
This problem has been resolved in version 1.2.1
12/22/2002.
|
Fixed
|
12/20/2002
|
stec.xpos.Index.create() improperly sets the keys
index file's length when a fixed number of keys
index pages was specified.
This problem has been resolved in version 1.2.1
12/22/2002.
|
Fixed
|
12/20/2002
|
stec.xpos.Index.create() improperly sets the values
index file's length when a fixed number of values
index pages was specified.
This problem has been resolved in version 1.2.1
12/22/2002.
|
Fixed
|
12/19/2002
|
stec.xpos.ObjectStore.expand() improperly sets the
value of the file length volume header resulting in
the store no longer being accessible.
This problem has been resolved in version 1.2.1
12/22/2002.
|
Fixed
|
12/19/2002
|
stec.xpos.Index.expand() improperly sets the
value of the file length volume header resulting in
the index no longer being accessible.
This problem has been resolved in version 1.2.1
12/22/2002.
|
Fixed
|
11/22/2002
|
Starting with version 1.2.0 12/03/2002
ObjectStoreEnumeration no longer automatically locks
keys.
Now ObjectStoreReference.keys(with_locking),
ObjectStoreReference.keys(filter, with_locking),
ObjectStore.elements(with_locking),
ObjectStore.elements(filter, with_locking) can be used
to specify whether locking is enabled.
|
Info
|
11/22/2002
|
Starting with version 1.2.0 12/03/2002 object store
enumerations requires call to close() when the
enumeration is no longer needed.
|
Info
|
11/20/2002
|
Fixed bug in ObjectStoreEnumeration that resulted in
dead-locks when the object store is being accessed by
multiple threads.
This problem has been resolved in version 1.2.0
12/03/2002.
|
Fixed
|
01/29/2002
|
Servertec Persistent Object Store version 1.0.0 throws
java.lang.NullPointerException when an object store
is accessed concurrently by multiple threads.
This problem has been resolved in version 1.0.1
02/04/2002.
|
Fixed
|
01/31/2002
|
Concurrent access by multiple threads results in data
store and mapper corruption.
This problem has been resolved in version 1.0.1
02/04/2002.
|
Fixed
|
01/31/2002
|
Because of changes to the format of an object store
introduced in
Servertec Persistent Object Store 1.0.1 02/04/2002,
POS Employees Servlet in Samples included in
Servertec Internet Server 1.10.3 will throw
javax.servlet.ServletException when used with
Servertec Persistent Object Store 1.0.1 or later
to access employees.htstore and employees.htmapper.
Servertec Persistent Object Store 1.0.1 02/04/2002
includes a new version of the employees store that
resolves this problem.
To use the new verion of the employees store, replace
iws_dir\samples\employees\employees.htstore and
iws_dir\samples\employees\employees.htmapper with
updated store included in pos_dir\samples\employees.
Where iws_dir is the directory where
Servertec Internet Server was installed and pos_dir
the directory where Servertec Persistent Object Store
was installed.
|
Info
|