Thanks for the prompt reply. 1) I was using 1.72-rc2 will try with 1.7.4 2) So in this case, I will have a non-abstract Java class (since I need to create embedded instances of it) but will use the Schema API after auto-generation to mark those classes as abstract?
CNM On Wednesday, June 25, 2014 3:02:34 PM UTC+5:30, Lvc@ wrote: > > Hi, > 1) what release are you using? Please use last GA 1.7.4. > 2) Setting the class as "abstract" in OrientDB schema is the only way to > avoid cluster creation. > > Lvc@ > > > > On 25 June 2014 08:06, CNM <[email protected] <javascript:>> wrote: > >> I have two questions: >> 1) I'm using the Object API and have an issue with Abstract classes not >> getting marked as abstract when the schema is generated from those classes. >> Is this a known issue or am I doing something wrong. >> 2) There are cases where a class is not abstract (in the Java sense) but >> will always be used only in embedded form (i.e. Embeddable JPA annotation) >> - so they will not have an independent identity from their parent. Is there >> a way to prevent OrientDB from creating clusters on these classes as well? >> >> CNM >> >> -- >> >> --- >> You received this message because you are subscribed to the Google Groups >> "OrientDB" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
