Hi, Unfortunately we don't have such Embeddable tag, even if it could be useful. May you open a new issue for that?
Lvc@ On 25 June 2014 15:50, CNM <[email protected]> wrote: > 1) This issue is fixed in 1.7.4 thanks! > 2) I tried setting the abstract property on the schema after registering > the classes but got the following error: > > Exception in thread "main" > com.orientechnologies.orient.core.exception.ODatabaseException: Error on > reading records size for cluster with id '18' > > at > com.orientechnologies.orient.core.db.raw.ODatabaseRaw.getClusterRecordSizeById( > ODatabaseRaw.java:399) > > Perhaps this is not a supported scenario. In a nutshell, what I want to do > is to not create clusters for java classes that are not abstract (because > they can have instances), but will never have their own identity. Ideally, > if a class is marked "Embeddable", OrientDB should avoid creating a cluster > (similar to the class being marked abstract). > > > On Wednesday, June 25, 2014 5:20:55 PM UTC+5:30, CNM wrote: >> >> 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]> 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]. >>>> 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. > -- --- 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.
