i really like your generator.
i have a special case where i have an @Embedded inside an @Embeddable. this leads to the problem that it i get an attribute not found error because it is generated as #{entity.name} but it should be #{entity.embeddable.name.en} and #{entity.embeddable.name.en}. i guess also the creation and the edit will not work :(
is it possible for you to look into this problem? this would be great :)
best, mike.
the structure is as follows:
@Entity
public class Entity implements Serializable {
...
@Embedded
private NameDescription nameDescription = new NameDescription();
...
}
@Embeddable
public class NameDescription implements Serializable {
...
@Embedded
@AttributeOverrides({
@AttributeOverride(name="en", column=@Column(name="name_english", nullable=false)),
@AttributeOverride(name="de", column=@Column(name="name_german"))
})
private Translation name = new Translation();
Hi Michael. First off, thank you for taking your time out and testing my plugin. I am happy that you like it.
I have to say that this whole Embeddable issue was quite something to get to work in the first place. As I have mentioned in other sections of this project, this is a fork of the original JSF Plugin, and the JSF Pages wizard in particular, which completely failed in this department.
That said, I would like you to either email me or post here an SQL Schema that I can use to test your case with. I assume that your entities were generated by the IDE from an existing database. So maybe you could post the SQL of that database or make one up with that particular case? And I will also try to replicate this here.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm looking at your code snippets again and have a feeling this is related to the @AttributeOverrides annotations you have there. Could you please try out your code without these overrides to see if this issue is related to that? There is a also good chance that this misbehavior is inherited from the JSF Plugin module. So could you also please try your entities with the default NetBeans JSF Pages from Entity Classes wizard? Does that exhibit the same behavior?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
hi,
i really like your generator.
i have a special case where i have an @Embedded inside an @Embeddable. this leads to the problem that it i get an attribute not found error because it is generated as #{entity.name} but it should be #{entity.embeddable.name.en} and #{entity.embeddable.name.en}. i guess also the creation and the edit will not work :(
is it possible for you to look into this problem? this would be great :)
best, mike.
the structure is as follows:
@Entity
public class Entity implements Serializable {
...
@Embedded
private NameDescription nameDescription = new NameDescription();
...
}
@Embeddable
public class NameDescription implements Serializable {
...
@Embedded
@AttributeOverrides({
@AttributeOverride(name="en", column=@Column(name="name_english", nullable=false)),
@AttributeOverride(name="de", column=@Column(name="name_german"))
})
private Translation name = new Translation();
...
}
@Embeddable
public class Translation implements Serializable {
...
@Column(name="en", nullable=false)
private String en = "unnamed";
@Column(name="de", nullable=false)
private String de = "unbenannt";
...
}
Hi Michael. First off, thank you for taking your time out and testing my plugin. I am happy that you like it.
I have to say that this whole Embeddable issue was quite something to get to work in the first place. As I have mentioned in other sections of this project, this is a fork of the original JSF Plugin, and the JSF Pages wizard in particular, which completely failed in this department.
That said, I would like you to either email me or post here an SQL Schema that I can use to test your case with. I assume that your entities were generated by the IDE from an existing database. So maybe you could post the SQL of that database or make one up with that particular case? And I will also try to replicate this here.
Hi Mike,
I'm looking at your code snippets again and have a feeling this is related to the
@AttributeOverridesannotations you have there. Could you please try out your code without these overrides to see if this issue is related to that? There is a also good chance that this misbehavior is inherited from the JSF Plugin module. So could you also please try your entities with the default NetBeans JSF Pages from Entity Classes wizard? Does that exhibit the same behavior?