|
||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD | |||||||||
java.lang.Objectorg.apache.directory.server.core.entry.ServerEntrySerializer
public class ServerEntrySerializer
| Constructor Summary | |
|---|---|
ServerEntrySerializer(Registries registries)
Creates a new instance of ServerEntrySerializer. |
|
| Method Summary | |
|---|---|
java.lang.Object |
deserialize(byte[] bytes)
Deserialize a ServerEntry. |
byte[] |
serialize(java.lang.Object object)
This is the place where we serialize entries, and all theirs elements. |
| Methods inherited from class java.lang.Object |
|---|
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
| Constructor Detail |
|---|
public ServerEntrySerializer(Registries registries)
registries - The reference to the global registries| Method Detail |
|---|
public byte[] serialize(java.lang.Object object)
throws java.io.IOException
This is the place where we serialize entries, and all theirs
elements. the reason why we don't call the underlying methods
(ServerAttribute.write(), Value.write()) is that we need
access to the registries to read back the values.
The structure used to store the entry is the following :
NOTE :This should be unnecessary, as the DN should always exists
serialize in interface Serializerobject - Object to serialize
java.io.IOException
public java.lang.Object deserialize(byte[] bytes)
throws java.io.IOException
deserialize in interface Serializerbytes - the byte array containing the serialized entry
java.io.IOException - if we can't deserialize the ServerEntry
|
||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD | |||||||||