Hi Calin, Short answer is: no. Long answer is: Not with the current state of the orion-xdoclet module. AFAIK, It works just if you use specific names for the foreign keys(the name of the foreign table, if I recall correctly) and you just specify in xdoclet that there's a relationship. XPetstore is an example of an application that is deployed with XDoclet in Orion and it works this way. Some people on the list said it would look at the topic if we could tell them exactly how we wanted the descriptors to look, but as I have no experience with Orion descriptors I could not help much. May be if you know how the descriptors should look like, you could help them fix the module, unless they are waiting for XDoclet 2 to start from scratch. Good luck, D.
> I am posting this question again; maybe somebody will answer this time: > Is there a tag for Explicit Mapping of Relationship Fields to the > Database for @oc4j/orion? > Something like the jboss ones: > * @jboss.relation > * fk-column="addr_id" > * related-pk-field="id" > * fk-contraint="no" > > and > > * @jboss.target-relation > * fk-column = "license_id" > * related-pk-field = "id" > * fk-constraint = "no" > > Thank you, > Calin Lupa -- This message was sent using Sake Mail, a web-based email tool from Endymion Corporation. http://www.endymion.com/products/sake
|
I am posting this question again; maybe somebody will answer this time:
Is there a tag for Explicit Mapping of Relationship Fields to the Database for @oc4j/orion?
Something like the jboss ones:
* @jboss.relation * fk-column="addr_id" * related-pk-field="id" * fk-contraint="no"
and
* @jboss.target-relation * fk-column = "license_id" * related-pk-field = "id" * fk-constraint = "no"
Thank you, Calin Lupa
|
