{"id":7521,"date":"2012-09-14T15:30:54","date_gmt":"2012-09-14T10:00:54","guid":{"rendered":"http:\/\/www.tothenew.com\/blog\/?p=7521"},"modified":"2016-12-19T15:16:41","modified_gmt":"2016-12-19T09:46:41","slug":"mapping-duplicate-domain-class-name-having-different-packages-using-autoimport-in-grails","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/mapping-duplicate-domain-class-name-having-different-packages-using-autoimport-in-grails\/","title":{"rendered":"Mapping duplicate domain class name having different packages using autoImport in Grails"},"content":{"rendered":"

Hi,
\n
\nRecently one of my friend asked me whether there is a mechanism in grails to handle the use-case where we have different packages but having same domain name. Here we are having duplicate domain class names in different package and by default the domain classes are auto-imported in HQL queries which doesn’t required to specify whole class name. Hence due to it class name are no longer unique because of this it cause DuplicateMappingException<\/strong><\/em> in our case. For this I refer my friend to set autoImport<\/a> false in mapping.
\n
\nGrails provide us a mapping key named ‘autoImport<\/a>‘. We can disable the auto-import for any one of the domain or both which will fix our problem to some extent. Lets see how it helps :
\n
\nSuppose we have 2 packages named :
\n1. com.tarun.poc.project <\/strong><\/em> having Domain named “Issue”.<\/strong>
\n[groovy]
\npackage com.tarun.poc.project
\nclass Issue {
\n String summary
\n static constraints = {
\n }
\n}
\n[\/groovy]
\n2. com.tarun.poc.company<\/strong><\/em> having Domain named “Issue”.<\/strong>
\n[groovy]
\npackage com.tarun.poc.company
\nclass Issue {
\n String description
\n static constraints = {
\n }
\n}
\n[\/groovy]<\/p>\n

When you run your app you will recieve the exception some thing like this :
\n[groovy]
\nnested exception is org.hibernate.DuplicateMappingException: duplicate import: Issue refers to both com.tarun.poc.project.Issue and com.tarun.poc.company.Issue
\n[\/groovy]<\/p>\n

Now we add autoImport to the mapping of domain ‘Issue’<\/strong> one or both and set it to false<\/strong> as specified below :
\n[groovy]
\npackage com.tarun.poc.project
\nclass Issue {
\n String summary
\n static constraints = {
\n }
\n static mapping = {
\n autoImport false
\n table ‘project_issue’
\n }
\n}
\n[\/groovy]<\/p>\n

It will fix your problem regarding ‘DuplicateMappingException’. If you see above we have also specified table mapping<\/a> because if we didn’t specify table mapping it will create a single table in database with name ‘issue’ and having properties of both the domains into that table.<\/p>\n

Hence to create different tables for Domain Class or customizes the name of the database table associated with the domain class we used table mapping<\/a>.<\/p>\n

Hope it helps \ud83d\ude42
\n
\nThanks,
\nTarun Pareek
\ntarun@intelligrape.com<\/p>\n

More Blogs by Me<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

Hi, Recently one of my friend asked me whether there is a mechanism in grails to handle the use-case where we have different packages but having same domain name. Here we are having duplicate domain class names in different package and by default the domain classes are auto-imported in HQL queries which doesn’t required to […]<\/p>\n","protected":false},"author":20,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":1},"categories":[7],"tags":[967,965,969,968,4840,966],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/7521"}],"collection":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/users\/20"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/comments?post=7521"}],"version-history":[{"count":0,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/7521\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/media?parent=7521"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/categories?post=7521"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/tags?post=7521"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}