EJB CMP/CMR example with JBoss+Xdoclet
For the ArticleBean, there is not much special, since the relation mapping is unidirectional. If it would have been bidirectional, we would have found similar Xdoclet tags, where we would have paid special attention on the fact that the name of the relationship was equal in both files. Since we will see this in a forthcoming post on one-to-many relationship mappings, I’ll postpone it here.
The only remarkable thing may be that I managed to assign the foreign-key in the ArticleBean a primary-key role at the same time! Of course, this is possible because of the one-to-one mapping only.
/**
* Returns the publicationIDfk
* @return the publicationIDfk
*
* @ejb.persistent-field
* @ejb.persistence
* column-name="publication_id_fk"
* sql-type="VARCHAR"
* @ejb.pk-field
* @ejb.interface-method
*
*/
public abstract java.lang.String getPublicationIDfk();
/**
* Sets the publicationIDfk
*
* @param java.lang.String the new publicationIDfk value
*
* @ejb.interface-method
*/
public abstract void setPublicationIDfk(java.lang.String publicationIDfk);
-
Comments are closed
-
#2 written by Carola 7 years ago
Hi everyone:
I would like to know if there’s possible to generate querys in the .java’s bean with xdoclect, something like Jboss IDE or hibernate. I must define relationships and create new querys and can’t do enything of that with my Lomboz Eclipse plugin and Jboss server.
I would be greateful at any kind of help
-
Regarding Comment 4, that’s because it’s after the “@jboss.target-relation” tag, which refers to the blind side of the relation. In the case which you mentioned, one would use the “@jboss.relation” tag, which makes it work from the other side.
It took me very long to figure this out…somehow most tutorials on the net use that kind of example with the CMR Relation on the blind side, which i personally find not very intuitive for a first example. When trying it with the tags on the side with the foreign key column this produces “unknown column in where query” exceptions.
-
#4 written by Breno Leitao 8 years ago
I did it and it works correctly (after some hacks
)).
Now i want to make tests around it. need i use cactus? is there another solution?
I dont want to kludge without another ejb.
Thank you
Breno Leitão.
http://lcr.icmc.usp.br -
#5 written by Arne v.Irmer 8 years ago
For anyone who searches for good example code:
Maybe you like to look at
http://xpetstore.sourceforge.net/
It is quite simple but has no bedirection m:n relationship. -
#6 written by Arne v.Irmer 8 years ago
I got it!!!!
“ss� and me have the following problem:
XDoclet generates an empty {field-name} and {column -name}.
Here is the reason for that behaviour:
We got the source via copy and paste from this website. This leads us to the following line:
related-pk-field="table1ID�
The closing quotation mark is non ASCII! This confuses XDoclet. Just replace it with the correct one (“) and everything works properly.
Yours
Arne -
#7 written by Zeger Hendrikse 8 years ago
This example is part of quite a large project in Eclipse, hence it is not possible to compose such a JAR instantly. However, I think it is a very good idea. Moreover, the statistics show that many people are struggling with these issues and are consulting my post.
Although I cannot promise to deliver the JAR file tomorrow, I’ll do my best to make it available soon. If so, I’ll make a new post, instead of changing this one. Of course, I’ll leave a comment referring to the new post.
If anyone else already has such a JAR file (preferrably based on my example) and is willing to share his/her efforts with the rest of the world, please let me know.
Regards,
-
#8 written by Arne v.Irmer 8 years ago
-
#9 written by Arne v.Irmer 8 years ago
-
#10 written by Zeger Hendrikse 8 years ago
From your comment I cannot see what you find confusing. I did not post the database schema, since the intention was to let the container create the schema for me. But now that the schema has been created, I can post it, of course!
An article is created in the Hypersonic database with this SQL statement:
CREATE TABLE ARTICLE(PUBLICATION_ID_FK VARCHAR(256) NOT NULL,TITLE VARCHAR(256),JOURNAL VARCHAR(256),YEAR INTEGER,VOLUME VARCHAR(256),NUMBER INTEGER,PAGES VARCHAR(256),MONTH VARCHAR(256),NOTE VARCHAR(256),CONSTRAINT PK_ARTICLE PRIMARY KEY(PUBLICATION_ID_FK))
The PUBLICATION_ID_FK is primary key and foreign key at the same time for the article table. This is sound, since we are dealing with a one-to-one relationship here.
A bibliography is created with:
CREATE TABLE BIBLIOGRAPHY(PUBLICATION_ID VARCHAR(256) NOT NULL,PUBLICATION_KEY VARCHAR(256),PUBLICATION_TYPE VARCHAR(256),ANNOTATE VARCHAR(256),CROSSREF VARCHAR(256),ABSTRACT VARCHAR(256),AFFILIATION VARCHAR(256),CONTENTS VARCHAR(256),COPYRIGHT VARCHAR(256),ISBN_ISSN VARCHAR(256),KEYWORDS VARCHAR(256),LANGUAGE VARCHAR(256),LCCN VARCHAR(256),LOCATION VARCHAR(256),SIZE INTEGER,MRNUMBER INTEGER,PRICE DECIMAL,URL VARCHAR(256),CATEGORY VARCHAR(256),CONSTRAINT PK_BIBLIOGRAPHY PRIMARY KEY(PUBLICATION_ID))
I hope this helped!
-
#11 written by Matt Robinson 8 years ago
-
#12 written by ss 8 years ago
Thanks a lot for the tutorial. however,
i used the following in my ant build script, but i had problems generating the <key -fields/> in jbosscmp-jdbc.xml.
And hence i had problems deploying my bean. It threw the following exception.org.jboss.deployment.DeploymentException: Atleast one role of a foreign-key mapped relationship must have key fields (or <primkey -field> is missing from ejb-jar.xml): ejb-relation-name=FolderMayContainDevices
Can you please help.
<relationships> <ejb -relation> <ejb -relation-name>FolderMayContainDevices <relation -table-mapping> </relation> <ejb -relationship-role> <ejb -relationship-role-name>FolderToDevices <ejb -relationship-role><ejb -relationship-role-name>DeviceToFolder</ejb> <key -fields> <key -field> <field -name> <column -name> </key> </key> </ejb> </ejb> <ejb -relation> <ejb -relation-name>FolderMayContainFoldersFolderToSubFolders <key -fields/> </key> <ejb -relationship-role><ejb -relationship-role-name>FolderToParentFolder</ejb> <key -fields> <key -field> <field -name></field> <column -name></column> </key> </key> </ejb> <!-- To add jboss relationships for beans not managed by XDoclet, add a file to your XDoclet merge directory called jbosscmp-jdbc-relationships.xml that contains the <ejb -relation> markups for those beans. --> </> </ejb>the build.xml was as follows:
<taskdef name = "ejbdoclettask" classname = "xdoclet.modules.ejb.EjbDocletTask" classpathref="xdoclet.class.path"/>ejbdoclettask destdir="${doclet.gensrc.dir}" mergedir="parent-fake-to-debug" excludedtags="@version,@author,@todo" addedtags = "@xdoclet-generated at ${TODAY},@copyright The XDoclet T eam, @author XDoclet,@version ${version}" ejbspec="2.0" force="false" verbose="false"> <fileset dir = "${source.dir}"> <include name = "**/*.java"/> </include> < !-- Comment the next two lines, if you do not want to e xpose the Beans via the Remote Interface --> <remoteinterface pattern= "{0}Remote"/> <homeinterface pattern = "{0}Home"/> <localinterface pattern = "{0}LocalInterface"/> <localhomeinterface pattern = "{0}LocalHome"/> <deploymentdescriptor destdir = "${jar.dir}/META-INF"/> <utilobject kind="physical" includeGUID="true"/> <entitypk /> <jboss version="4.0" destdir="${jar.dir}/META-INF" validatexml="false" generateRelations="true" /> </jboss></entitypk></utilobject></deploymentdescriptor></localhomeinterface></localinterface></homeinterface></remoteinterface></jboss></entitypk></utilobject></deploymentdescriptor></localhomeinterface></localinterface></homeinterface></remoteinterface></ejb> </remoteinterface></remoteinterface> -
#13 written by Janos Czako 8 years ago
- Comment Feed for this Post
Did it and worked. In fact the CMR element -Container Managed Relations- is an obvious missing point. Do you know where I can get some good sources for CMR?
Thanks!