BEFORE_DELETE Hook Problem

[wallyatkins]

OVERVIEW
This test demonstrates a bug in which an OrientDB BEFORE_DELETE hook receives an unpopulated iRecord when OObjectDatabaseTx.delete(Object) is called within a transaction.

ANALYSIS
The test fails due to a NullPointerException (NPE) being thrown in the BEFORE_DELETE hook, when ((ODocument)iRecord).getClassName() is used for a .equals() comparison - in the same manner as shown in OrientDB examples. This NPE occurs because getClassName() returns null, because the iRecord's fields are not populated when the onTrigger method is called.

ENVIRONMENT
BeforeDeleteHook.java implements a server side hook, with an onTrigger method for processing BEFORE_DELETE.
The client (TestHook.java) connects using the OrientDB remote protocol.
The delete method is called within an OrientDB transaction.

[wallyatkins]

This thread from the OrientDB Google Groups contains a sample project which demonstrates the issue.

https://groups.google.com/forum/#!topic/orient-database/1FF8NGoYRh8

[lvca]

Your test case passes against OrientDB 1.6.0-SNAPSHOT:

About to delete item with id: #9:0
Deleted Item_$$_javassist_0@cd11fa6

[wallyatkins]

Thanks Luca! Is there a set release date for OrientDB 1.6 yet? I saw something about mid September in the Google Groups. Is that still the plan?

[lvca]

Yes, it should be on September 24-26th.