|
I found this bug again in 3.1.0.GA, then I tested with 3.1.0.Beta1 and again. Please giveme a hint where to debug, and what to do. Thanks DocumentBuilderIndexedEntity contains a flag 'safeFromTupleId' which is set when the metadata is created. This flag is the used in MultiClassesQueryLoader to determine how to load objects. So there is definitely some code which should at least take care of the scenario. Need to check if there is a test case. There is actually a bug. After the split of DocumentBuilder into DocumentBuilderIndexedEntity and documentBuilderContainedEntity line 151 should have changed to safeFromTupleId = TwoWayString2FieldBridgeAdaptor.class.isAssignableFrom( idBridge.getClass() ); Where is DocumentBuilderIndexedEntity? Azael, this issue was fixed on Hibernate Search 3.1.1 Thanks for answering. I have a question but since I am newbie I only used the seam jars that are in, because it creates the project via seam-gen which generates all by itself. download Hibernate Search 3.1.1 and I put the libraries in my project or on jboss? excuse my newbie question This is not a forum. You should ask this kind of things on the Hibernate Search forum. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
I fixed this bug in 3.1.0.Beta1. Any change you can give it a try.